| commit | 72e13b2f01beb6105c6a74b66aa92bdc6d553a8e | [log] [tgz] |
|---|---|---|
| author | holte <holte@chromium.org> | Fri May 22 01:30:43 2015 |
| committer | Commit bot <commit-bot@chromium.org> | Fri May 22 01:31:15 2015 |
| tree | 9610ba042d18fe8ee1be4fe1e04f228bc90c3a84 | |
| parent | 9e4a77490fbf479868554c45d8f85858b65a3213 [diff] |
Revert of Add ref-count on RenderViewHost for each new RenderFrameProxyHost. (patchset #4 id:60001 of https://codereview.chromium.org/1150793002/) Reason for revert: It looks like the new browser test fails on Win8 aura https://build.chromium.org/p/chromium.win/builders/Win8%20Aura/builds/30026/steps/content_browsertests/logs/RenderFrameHostManagerTest.CleanupOnCrossProcessNavigation Original issue's description: > Add ref-count on RenderViewHost for each new RenderFrameProxyHost. > > Currently, only RenderFrameHosts are ref-counting the associated RenderViewHost. > Since it is possible to have a RenderViewHost with no associated RenderFrameHost > (for example a cross-process window opener/openee relationship), it should > be taken into account that the associated RenderFrameProxyHost is also > a ref-counting the RenderViewHost. > The goal of this CL is to allow for that, even though it isn't currently > the case. It is a small step towards removing swapped out RenderFrameHosts. > > BUG=357747 > > Committed: https://crrev.com/8542185bbb9fd0c0e7d0240c64403d2e4cea39f2 > Cr-Commit-Position: refs/heads/master@{#331016} TBR=creis@chromium.org,nasko@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=357747 Review URL: https://codereview.chromium.org/1157563002 Cr-Commit-Position: refs/heads/master@{#331041}