diff options
| author | tc@google.com <tc@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-06-10 21:19:58 +0000 |
|---|---|---|
| committer | tc@google.com <tc@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-06-10 21:19:58 +0000 |
| commit | 8e53730a2199f914cbd79cf72c363ad33aea0802 (patch) | |
| tree | 48b3d8d5f3ae6ebcafd2fe8444e5976592dcb125 /views/view_unittest.cc | |
| parent | 2248462eb24d976e2146aff311cccbc92352d0b4 (diff) | |
| download | chromium_src-8e53730a2199f914cbd79cf72c363ad33aea0802.zip chromium_src-8e53730a2199f914cbd79cf72c363ad33aea0802.tar.gz chromium_src-8e53730a2199f914cbd79cf72c363ad33aea0802.tar.bz2 | |
Fix a crash in linux if the renderer process dies too fast. On mac, we
just don't get the sad tab page.
If the renderer dies before it sends a ViewHostMsg_RenderViewReady message,
we never get the TAB_CONTENTS_CONNECTED, which in turn means that
TAB_CONTENTS_DISCONNECTED doesn't fire. If TAB_CONTENTS_DISCONNECTED
doesn't fire, we never initialize sad_tab_ in tab_contents_view_gtk.cc and
crash the browser process.
I found this crash on the crash server:
http://crash/reportdetail?
reportid=fb3a7bc60c67eb1e&product=Chrome_Linux&version=3.0.183.1&date=&signa
ture=TabContentsViewGtk::Invalidate()-534CC7
BUG=13715
Review URL: http://codereview.chromium.org/119395
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@18087 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'views/view_unittest.cc')
0 files changed, 0 insertions, 0 deletions