Updates:
Cc: b...@chromium.org
Comment #2 on issue 8030 by fin...@chromium.org: UI reliability crash in
WebContents::StopFinding
http://code.google.com/p/chromium/issues/detail?id=8030
Looks like WebContents::StopFinding is called on a NULLed out web_contents_
inside FindBarWin, which can only happen after a tab is dragged
out (if I am reading the code correctly). I cannot repro manually, but I'll
keep investigating.
chrome_2650000!WebContents::StopFinding+0x11
[src\chrome\browser\tab_contents\web_contents.cc @ 573]
chrome_2650000!FindBarWin::EndFindSession+0x2f
chrome_2650000!FindBarView::ButtonPressed+0x40
chrome_2650000!views::BaseButton::NotifyClick+0x1f
chrome_2650000!views::BaseButton::OnKeyReleased+0x32
chrome_2650000!views::RootView::ProcessKeyEvent+0x104
chrome_2650000!views::WidgetWin::OnKeyUp+0x40
chrome_2650000!views::WidgetWin::_ProcessWindowMessage+0x3eb
chrome_2650000!views::WidgetWin::WndProc+0xc3
user32!InternalCallWinProc+0x28
user32!UserCallWinProcCheckWow+0x150
user32!CallWindowProcAorW+0x98
user32!CallWindowProcW+0x1b
chrome_2650000!views::FocusWindowCallback+0x187
user32!InternalCallWinProc+0x28
user32!UserCallWinProcCheckWow+0x150
user32!DispatchMessageWorker+0x306
user32!DispatchMessageW+0xf
chrome_2650000!views::AcceleratorHandler::Dispatch+0x4f
chrome_2650000!base::MessagePumpForUI::ProcessMessageHelper+0x6c
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
