diff options
| author | mkosiba@chromium.org <mkosiba@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-12-04 15:44:01 +0000 |
|---|---|---|
| committer | mkosiba@chromium.org <mkosiba@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-12-04 15:44:01 +0000 |
| commit | 4352f70f703c920e10c9d689dcb7844b4ddf72b3 (patch) | |
| tree | 3aebed0406470937c2e9bd02f95204a4436c3bb3 /base | |
| parent | e003c2c77529d4b6b8b6169022d827b9c6dab0ca (diff) | |
| download | chromium_src-4352f70f703c920e10c9d689dcb7844b4ddf72b3.zip chromium_src-4352f70f703c920e10c9d689dcb7844b4ddf72b3.tar.gz chromium_src-4352f70f703c920e10c9d689dcb7844b4ddf72b3.tar.bz2 | |
[android_webview] Fix crash in ContentViewCore/ContentSettings.
Apparently it's possible for mHandler to run after .destroy has
been called on mContentViewCore.
Since the ContentViewCore.destroy() documentation states that no
other methods may be called on it after destroy() it seems like
the right fix is to add a check to the handler.
BUG=None
Review URL: https://chromiumcodereview.appspot.com/11412273
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170964 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base')
0 files changed, 0 insertions, 0 deletions