3 ms·
This has been like this since before chrome version 1.0 Chrome uses a multi-process architecture. So you have a process for the "browser", a process for each e
by Klathmon 10y ago
This has been like this since before chrome version 1.0
Chrome uses a multi-process architecture. So you have a process for the "browser", a process for each extension installed, a process for each tab, a process for the GPU renderer, processes for if it's pre loading a page in the background, etc...
Many of them share memory.
If you want a bunch of details about all of this, press "Shift + escape" while in chrome and it will open the chrome task manager which shows a bunch of this and more.