Reland "Extensions: Fix memory leak in ExtensionApiFrameIdMap."
This is a reland of 613ba331. This collided with r541891. Original change's description: > Extensions: Fix memory leak in ExtensionApiFrameIdMap. > > Currently in ExtensionApiFrameIdMap::UpdateTabAndWindowId and > ExtensionApiFrameIdMap::LookupFrameDataOnUI we don't check whether a > RenderFrameHost is alive, before storing it's frame data. It's possible that > such a RenderFrameHost never becomes alive, and hence we don't get any > OnRenderFrameDeleted notification for it. Since ExtensionApiFrameIdMap is a > singleton, this causes a memory leak. To fix, ensure that only live > RenderFrameHosts are tracked. > > Also ensure in InProcessBrowserTest::TearDown that ExtensionApiFrameIdMap is not > leaking memory for any browser test. > > BUG=817205 > > Change-Id: I78bf06cee7e10465f9eb5973ee8e59f525a74d93 > Reviewed-on: https://chromium-review.googlesource.com/951975 > Reviewed-by: Scott Violet <sky@chromium.org> > Reviewed-by: Devlin <rdevlin.cronin@chromium.org> > Commit-Queue: Karan Bhatia <karandeepb@chromium.org> > Cr-Commit-Position: refs/heads/master@{#541950} TBR=sky@chromium.org,rdevlin.cronin@chromium.org Bug: 817205 Change-Id: I7b3ac6806d0c747d439e74f80f623a7fd4412050 Reviewed-on: https://chromium-review.googlesource.com/956762 Commit-Queue: Karan Bhatia <karandeepb@chromium.org> Reviewed-by:Karan Bhatia <karandeepb@chromium.org> Cr-Commit-Position: refs/heads/master@{#542025}
Showing
Please register or sign in to comment