diff options
author | alexmos <alexmos@chromium.org> | 2015-04-29 16:10:37 -0700 |
---|---|---|
committer | Commit bot <commit-bot@chromium.org> | 2015-04-29 23:11:51 +0000 |
commit | dcbe3fb4ed2eff72578d362df739e165dac79dff (patch) | |
tree | a97c010e34c0d0157344c16b7d70c7eec51d12e7 /net | |
parent | 2e02ce16df4540728922aedf4a8955c0dd346228 (diff) | |
download | chromium_src-dcbe3fb4ed2eff72578d362df739e165dac79dff.zip chromium_src-dcbe3fb4ed2eff72578d362df739e165dac79dff.tar.gz chromium_src-dcbe3fb4ed2eff72578d362df739e165dac79dff.tar.bz2 |
Ensure proxies are recreated after navigating to killed process.
This fixes the crash in CreateFrameProxy due to non-existent parent
proxies. This happened when an OOP frame's renderer crashed,
was recreated due to another navigation, and then other renderers
added new child frames which triggered new proxies to be created
in the restored process.
Before this fix, only the top frame's proxy was restored, and the
other proxies were skipped over in CreateProxiesForSiteInstance
because their RFPHs existed, even though the RFPs didn't. This CL
modifies CreateRenderFrameProxy to also check whether the RFP is
live, and create it if necessary.
Doing this revealed that the render_frame_proxy_created_ flag wasn't
being properly set for proxies created as part of InitRenderView(), so
this CL also fixes that issue.
BUG=478892,476846
Review URL: https://codereview.chromium.org/1108183002
Cr-Commit-Position: refs/heads/master@{#327607}
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions