Updates:
Owner: [email protected]
Cc: [email protected]
Comment #7 on issue 8085 by [email protected]: new tab opened from a
parent page doesn't share the same process id with its parent
http://code.google.com/p/chromium/issues/detail?id=8085
Tracked it down. The correct SiteInstance is being used, but when the
renderer
crashed, the SiteInstance's RenderProcessHost was set to null. This caused
a new
process to be created the first time SiteInstance::GetProcess() was called,
which is
when the first same-site link is opened in a new window.
It used to be the case that a SiteInstance's process never changed, and I
think that
should still be the case. (That kept all the tabs with the same
SiteInstance in the
same process, even after a crash.) The changelist referenced below
(r11509) changed
that, which I think caused this bug. John said he's looking into a related
bug
(9379) and has ideas of how to fix it, so I'll switch this over to him.
I'm happy to
help more if it makes sense.
http://codereview.chromium.org/42054
--
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
-~----------~----~----~----~------~----~------~--~---
