Status: Untriaged Owner: [email protected] Labels: Type-Bug Pri-2 OS-All Area-Misc
New issue 7046 by [email protected]: Re-use renderer processes intelligently http://code.google.com/p/chromium/issues/detail?id=7046 Chrome has a limit to the number of renderer processes it will create, to avoid overloading the user's machine. If this limit is reached, Chrome randomly assigns new tabs (i.e., SiteInstances) to existing processes, as long as the Profile matches. In this case, we should try to more intelligently assign new SiteInstances to existing renderer processes. For example, we should try to assign a new SiteInstance to a renderer process showing pages from the same site, if one already exists. This will help improve isolation between sites. The heuristics should be smart enough to avoid overloading a single renderer process, though. For example, putting all Google Apps into a single process will degrade their responsiveness. -- 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 -~----------~----~----~----~------~----~------~--~---
