diff options
| author | sky@chromium.org <sky@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-02-05 19:40:07 +0000 |
|---|---|---|
| committer | sky@chromium.org <sky@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-02-05 19:40:07 +0000 |
| commit | 85335d37785dc01fa75356af9a307022bd401f20 (patch) | |
| tree | 474934d03a09e2a73942c8d38dacc8b97346bb7b /base/file_util_win.cc | |
| parent | 83f855ac31bc2554f52ffe826681e2759a721bbd (diff) | |
| download | chromium_src-85335d37785dc01fa75356af9a307022bd401f20.zip chromium_src-85335d37785dc01fa75356af9a307022bd401f20.tar.gz chromium_src-85335d37785dc01fa75356af9a307022bd401f20.tar.bz2 | |
Attempt at fixing possible shutdown crash
In some situations we can enter ~BrowserView with WebContents in the
tab strip. There is code that attempted to deal with this, but by the
time we get to ~BrowserView it's really too late to attempt to delete
the WebContents. Reason being doing anything with the TabStrip more
often than not results in calling back to the BrowserView and related
classes. So, this shutdown really needs to be done earlier on.
I'm moving it to when the frame is being destroyed, which means all
view/layout classes are still valid.
BUG=176556
TEST=covered by test now.
R=ben@chromium.org
Review URL: https://codereview.chromium.org/154633003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@249083 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base/file_util_win.cc')
0 files changed, 0 insertions, 0 deletions