Comment #10 on issue 9364 by [email protected]: REGRESSION: Opening multiple tabs with same URL all share the same process id http://code.google.com/p/chromium/issues/detail?id=9364
In a nutshell, the problem is that all tabs that open with a DOM UI page (e.g., new tab page) are now sharing a BrowsingInstance, rather than having their own BrowsingInstances. There can only be one SiteInstance per site within a BrowsingInstance, so this causes all pages from the same site to be in the same process. Here's what happened, in more detail. Before r11925, DOM UI pages were a different tab type than web pages, and the two tab types always had disjoint BrowsingInstances and SiteInstances. Navigating from a DOM UI page to a web page was like creating a new tab, so it created a new BrowsingInstance for the web page. This let us create separate processes for same-site pages in different BrowsingInstances. Because we could assume DOM UI pages had their own tab type, we were getting away with a trick that consolidated all DOM UI pages into a single BrowsingInstance and SiteInstance. That meant we only needed one process for all the DOM UI pages, which was nice for cutting down the number of processes. (This trick is in BrowsingInstance::ShouldUseProcessPerSite().) After r11925, though, DOM UI pages have the same tab type as web pages, so they end up sharing a BrowsingInstance. The trick mentioned above put all of the DOM UI pages in the same BrowsingInstance, so all web pages ended up in the same one as well. -- 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 -~----------~----~----~----~------~----~------~--~---
