If you’ve ever taken a peek in Task Manager while running Google Chrome, you may have been surprised to see that the number of chrome.exe entries radically exceeded the number of actual Chrome windows you had open. What’s the deal with all those processes?
You can read the details here:
Google Chrome takes advantage of these properties and puts web apps and plug-ins in separate processes from the browser itself. This means that a rendering engine crash in one web app won’t affect the browser or other web apps. It means the OS can run web apps in parallel to increase their responsiveness, and it means the browser itself won’t lock up if a particular web app or plug-in stops responding. It also means we can run the rendering engine processes in a restrictive sandbox that helps limit the damage if an exploit does occur.
Basically, each tab has one process unless the tabs are from the same domain. The renderer has a process for itself. Each plug-in will have one and so will each extension that is active.
Get full forum access here! || Follow us || Rules || 1 fee, download them all!
Giin70 Said:"im busier than a 3 legged cat on a frozen pond scratching for a place to poop..."
He also Said:"Maybe we can ship yall off to mamby pamby land to look to self confidence, ya jackwagon."
Then"your about as useless as tits on a boar
And:"headspace and keyboard timing issue on end user end"
Always have a back up plan for your back up plan.
My Pc Specs: My Rig!
Giin70 Said:"im busier than a 3 legged cat on a frozen pond scratching for a place to poop..."
He also Said:"Maybe we can ship yall off to mamby pamby land to look to self confidence, ya jackwagon."
Then"your about as useless as tits on a boar
And:"headspace and keyboard timing issue on end user end"
Always have a back up plan for your back up plan.
My Pc Specs: My Rig!