[Chromecast] Fix Lifetime issue between CastWindowManager and CastBrowserProcess
CastWindowManager are used in chromecast code with the assumption that it outlives the browser process code, meanwhile CastWindowManager is reset before CastBrowserProcess, causing lifetime issues. Since CastWindowManager is owned by CastBrowserMainPart and is created before CastBrowserProcess, the reasonable fix is to swap the order to reset CastWindowManager after CastBrowserProcess. Because CastScreen is used by WindowManager during tear down, its ownership is moved to CastBrowserMainPart. This fixes cast_shell_browsertests. Bug: b/144778077, b/131312670 Test: CQ Change-Id: Iee03600138c3d7d9324ba3971d1aad816239115b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1928897Reviewed-by:Sean Topping <seantopping@chromium.org> Reviewed-by:
Daniel Nicoara <dnicoara@chromium.org> Commit-Queue: Jiaqi Han <jiaqih@google.com> Cr-Commit-Position: refs/heads/master@{#720282}
Showing
Please register or sign in to comment