Explaining CPU usage

[sebi]

Hello guys,

Few of you, overtime, asked me they wanted to understad the CPU usage in chrome, and why a number of processes are opened, etc.
Well, this is a chrome-specific behavior, specially designed so that if a website crashes, all others are NOT affected. And this is good.

Basically, for each NEW SITE that you open (either if in a new tab or if in a new window or popup or if a frame inside other site), at least 1 new chrome.exe process will exist for it.
Also, for each browser extension that is added inside chrome, 1 new chrome.exe process gets created.

For example, first time you start camerolla app, chrome will start by default with 11 distinct processes, each having a specific job, as you can see in this image:

Now, let me explain what's there.
As you can see from Chrome's task manager, and also from Windows' task manager, there are:

• 6 active processes
  
• 5 background processes
  

The active processes are sessions of chrome that deal with pages and extensions. For example, out of the 6 active processes in the image above, 2 of them are because of Lovense extension, one is because of Camerolla assistant, another one is of YouTube audio-only. The remaining 2 are of main chrome.

The background processes are sessions of chrome that render the pages in background (paralel), or utilities that monitor crashes, etc, as you will see in the next image. 2 of them for example, are related with the new-tab-page that you see when logging-in.



As i highlighted in RED, the background processes:

• 3 are renderers (which render the HTML of websites into visible content)
  
• 1 is a utility
  
• and one is taking care of reporting crashes
  

Now... after the user logsin in the app, 1 new process will show-up, which takes care of monitoring user's online times etc:

Now, if we also open a new site, you will see that the active processes will increase from 7 to 8, because we will open a new tab (so, a new chrome.exe process):

Now, to even better explain this, if we open 2 more tabs with livejasmin, you will see 2 more processes... so the number of active chrome.exe processes will change from 8 to 10.

Now, for the power of example... let's simulate that one of the 3 livejasmin tabs crashes (we will the TAB process from internal Chrome's task manager). You will learn that all other websites are still working, but only the tab that we killed will have crashed, and that the number of active processes decreases from 10 to 9:

As about the NEW-TAB-PAGE from where the user (model or staff) opens the camsites... that one uses 2 background processes:

• one for rendering the page with camsites, time online, time in break, etc
  
• the other for rendering the frame with the periodical earnings of the model
  

If you close that new-tab-page, you will see that the number of background processes decreases from 5 to 3:

Now... please understand that:

• Chrome in our standard manner now usually uses at least 10 processes at minimum. This doesn't mean that all of them are CPU intensive, no... but they are indeed processes that might scare you. As explained, out of the 10, 2 are of Lovense extension, one is of Camerolla extension, one is of YuTube audio only extension.
  
• If you also add more extensions to chrome, those will increase the number of processes, depending on the extensions you add.
  
• Each TAB page (or window) ads at least 1 more process. So if the model opened 5 websites and 5 youtube pages, and 1 google translate and one facebook... that means 5+5+1+1 = 12 more CPU processes added to those initial 10.
  
• A website like MyFreeCams which uses frames, most probably will add 2 processes or so. Might also be valid for CamContacts for example
  
• Also, some websites (like chaturbate for example) are distributin ADS as iframes... and each add comes with a cost of a new CPU process in chrome! Even tracking via Google which gets added on sites might also add a new CPU process in chrome, as you can learn from the picture bellow:
  

I honestly hope that you understand, from this topic, how Chrome wroks.
Please note that Firefox works in a simila fashion, but in its case, the number of processes is smaller... but it is better exposed to crash-risks compared to Chrome due to its design.