diff options
| author | finnur@google.com <finnur@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-02-26 00:08:22 +0000 |
|---|---|---|
| committer | finnur@google.com <finnur@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-02-26 00:08:22 +0000 |
| commit | 29d25005a8778783608c89015bdfbd25cadb7d3f (patch) | |
| tree | 05bad179b9beaf1b333921c17bc799e17d42ec7b /chrome/browser/views/find_bar_win.cc | |
| parent | b0beaa66afc6a6127440a65b56ce3967c8852e40 (diff) | |
| download | chromium_src-29d25005a8778783608c89015bdfbd25cadb7d3f.zip chromium_src-29d25005a8778783608c89015bdfbd25cadb7d3f.tar.gz chromium_src-29d25005a8778783608c89015bdfbd25cadb7d3f.tar.bz2 | |
We can get into a state where the automation framework sends a search string, which ends up in a handler in the FindBarView that has already been destroyed, causing a crash.
We now explicitly null the controller for the text field when destroying the view so that if it is still receiving messages they will be ignored by the view.
(I can't reproduce this bug manually or by running the automation testing locally, but this is an attempt to fix the crash by using the information gathered from looking at the crash dump).
Review URL: http://codereview.chromium.org/27172
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@10413 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/views/find_bar_win.cc')
0 files changed, 0 insertions, 0 deletions