Reland "Reuse process on history navigations between same-site cross-BI pages"
This is a reland of b9f1aa01 The CL was previously reverted due to a flaky check on whether a process is still alive or not, which is fixed in this CL by adding a RenderFrameDeletedObserver and waiting until the process is actually deleted before checking. See fix: https://chromium-review.googlesource.com/c/chromium/src/+/2323086/1..2/content/browser/frame_host/render_frame_host_manager_browsertest.cc Original change's description: > Reuse process on history navigations between same-site cross-BI pages > > See crbug.com/1096135 for context. When doing same-site navigations, we > might do a proactive BrowsingInstance swap, but we will reuse the > renderer process whenever we can. On history navigations between pages > that are same-site but have different BrowsingInstances (not only on > cases that are caused by proactive BI swap), we should try to reuse the > renderer process. > > Bug: 1096135 > Change-Id: I58f72bedecbbf94e4e05218bb9c15970a502d8a9 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2282553 > Commit-Queue: Rakina Zata Amni <rakina@chromium.org> > Reviewed-by: Charlie Reis <creis@chromium.org> > Reviewed-by: Alex Moshchuk <alexmos@chromium.org> > Cr-Commit-Position: refs/heads/master@{#792195} Bug: 1096135, 1110281 Change-Id: I2c1ad20a73ad194980dfb2ab4caef29d2e1113d2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2323086Reviewed-by:Alex Moshchuk <alexmos@chromium.org> Reviewed-by:
Charlie Reis <creis@chromium.org> Commit-Queue: Rakina Zata Amni <rakina@chromium.org> Cr-Commit-Position: refs/heads/master@{#792492}
Showing
This diff is collapsed.
Please register or sign in to comment