Fixe use after free during destruction
Problem scenario happened because destroying a tab was triggering updating another tab. When the other tab updated various BrowserWindow methods were called when BrowserView was in a bad state (part way through destruction). In theory if detaching tried to update state we would end up in the same situation as this fixes, but that seems less likely. BUG=236389 TEST=covered by test now R=avi@chromium.org Review URL: https://chromiumcodereview.appspot.com/23800003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@221337 0039d316-1c4b-4281-b951-d872f2087c98
Showing
Please register or sign in to comment