Comment #6 on issue 4629 by [EMAIL PROTECTED]: Chrome: Crash Report - Stack  
Signature: WebContents::ShowWidget(int,gfx::Rect const &)-92C9CD
http://code.google.com/p/chromium/issues/detail?id=4629

A couple of crashes didn't show a11y on the stack, but many other crashes  
do. I believe the a11y
code is triggering us to be reentrant when we aren't set up to be  
reentrant. Specifically when we
show a window (widget_view->ShowWindow(SW_SHOW)) it appears that the a11y  
code gets called back.
This can trigger us to block, so that by the time control returns back to  
showwindow the
widget_host has been destroyed and when we invoke Init() on it we get the  
crash.

The trace at
http://0.queryserver.queryserver.crash.fp.borg:25571/reportdetail?
reportid=bfa9248d6adcaa09&product=Chrome&version=0.4.154.25&date=&signature=WebContents::ShowWidge
t(int,gfx::Rect+const+%26)-934F19 shows the following interesting bits.  
This is in reverse order
(top of the stack is last):

chrome_68a50000!WebContents::ShowWidget+0x114 <- first call to ShowWidget
user32!NtUserShowWindow+0xc
ntdll!KiUserCallbackDispatcher+0x2e
user32!__ClientCallWinEventProc+0x2a
tiptsf!CARET::ProcessCaretEvents+0x8c
tiptsf!CARET::_ProcessCaretEvents+0x25c
tiptsf!CARET::UpdateEditFieldState+0x28
tiptsf!CARET::UpdateMSAAEditFieldState+0x78
oleacc!AccWrap_LocationFix::accLocation+0x2b <- The ShowWindow call calls  
us back.
oleacc!AccWrap_Base::accLocation+0x2b
chrome_68a50000!BrowserAccessibility::accLocation+0x74
...
chrome_68a50000!WebContents::ShowWidget+0x118 <- another call to ShowWidget

Why are so many people hitting this and not just those that have turned on  
a11y? I suspect the
tablet drivers use a11y under the covers for tracking state.

-- 
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

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Chromium-bugs" group.
To post to this group, send email to chromium-bugs@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/chromium-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to