Comment #11 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
To fix this, I think we just need to change the trick we're using to consolidate DOM UI pages. We should make sure they end up in separate BrowsingInstances (and thus separate SiteInstances), but somehow ensure that they share the same RenderProcessHost under the covers. Navigating to a web page will then create a separate SiteInstance in the same BrowsingInstance. However, it's also extremely important that web pages never end up in the same process as DOM UI pages. We used to have a clean separation between the two because of the different tab types, but I'm concerned that there could be cases where a DOM UI page and a web page will share a process. Brett, can I ask why we decided to make them the same tab type? -- 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 -~----------~----~----~----~------~----~------~--~---
