diff options
author | jcivelli@chromium.org <jcivelli@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-05-06 04:32:58 +0000 |
---|---|---|
committer | jcivelli@chromium.org <jcivelli@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-05-06 04:32:58 +0000 |
commit | c71abb7a1027a4ef98dd55ac8064ac7aef5aa37d (patch) | |
tree | 25d8b9ad608cd1bf1207ebbc215e4e2acb244dfa /chrome/browser/automation/automation_provider.h | |
parent | 97a28ef93ae420282c3d877d18b2d363abe26ed4 (diff) | |
download | chromium_src-c71abb7a1027a4ef98dd55ac8064ac7aef5aa37d.zip chromium_src-c71abb7a1027a4ef98dd55ac8064ac7aef5aa37d.tar.gz chromium_src-c71abb7a1027a4ef98dd55ac8064ac7aef5aa37d.tar.bz2 |
Fix a crasher withe the AppLauncher on Linux.
On Linux, the WidgetGTK destruction is asynchronous.
The AppLauncher is deleted when the bubble is closing,
but the bubble is deleted when the WidgetGtk is destroyed.
So the bubble (and its DOMUI) is going away after the app launcher.
Since the app launcher is the TabContentsDelegate of the bubble tab,
the deleted app launcher could still be notified.
This CL ensures we NULL the TabContents' delegate when the AppLauncher
is deleted so it is not accessed.
Original review:
http://codereview.chromium.org/1985003/show
BUG=3068
TEST=On ChromeOS, open the app launcher and close it while it is loading.
Try several times, it should not crash.
Review URL: http://codereview.chromium.org/1996005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46551 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/automation/automation_provider.h')
0 files changed, 0 insertions, 0 deletions