After an initial dislike, I started using Google Chrome again on my notebook, but to my chagrin found that it was an even bigger memory hog than the trusty ol’ Firefox! Whilst with 3 of my oft-used sites open in Firefox it was at 96k of memory, Chrome with just the one tab open had 8 different chrome.exe processes in the task manager, with a combined memory footprint of 118k 👿
Now I know Chrome creates a separate process for each tab but with only 1 tab, why 8 processes? I started killing the processes, starting with the least memory usage first and look what I noticed:
Each Chrome Extension creates its own process! And each Chrome Plugin creates its own process! What the…
I don’t know if the multi-process architecture is the inherent “good stuff” about Chrome but yes, that does help in keeping the browser running even though a related extension or plugin or tab has crashed. But that comes at what price? What if it were an older PC with just the 512 MB of RAM and a not-so-fast processor? Chrome would just C(h)rawl!
Found this page at Chromium.org that says:
Chromium extensions will follow a multi-process architecture to share the same kind of stability and security that regular web pages have in Chromium. All of an extension’s code runs in a single process, separate from the browser
Good idea but dunno how useful it’ll be with older and slower pc’s.