Comment #3 on issue 14987 by albertod.zgz: On chrome startup with restore pages that were last open option is set, all the tabs from previous session are loaded into separate renderer processes. http://code.google.com/p/chromium/issues/detail?id=14987
This also happens in other situations, such as when using "Undo close tab". The problem can actually be much worse than it appears, specially considering there's a moderately low process limit (just 14 for 1GB or RAM). Consider the following scenario: You open 15 tabs from the same page to read them later. These are very lightweight text-only tabs, and they all get loaded into the same process. Now you close and reopen Chrome, restoring the tabs. Now each one goes into one process. You hit the process limit. This is wasteful already, but it gets worse: You leave that restored window aside and start browsing other pages. Since you're at the process limit, all new pages go into one of these processes. Now you lose most of the multi-process advantages: * Security isolation is reduced * Resource management is worsened. Even if you close the new tabs, the renderer processes will be kept around until you close the tabs in that old window (this also decreases security even further) As the number of tabs grows, you're in for an even worse mess, as tabs from different sites will get randomly mixed in processes after restore, and tabs from the same site will get spread across different processes which they share with other random stuff, which is inefficient and dangerous. The most visible issue however is the inefficiencies this creates, specially regarding memory - you basically have to close all the tabs to fix it. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
