Comment #4 on issue 4559 by [EMAIL PROTECTED]: Chrome: Crash Report -
Stack Signature:
BrowserAccessibilityManager::RequestAccessibilityInfo(int,int,int,tagVARIANT,long,long)-94A7D2
http://code.google.com/p/chromium/issues/detail?id=4559
After taking a look at the mini-dump, the dissassembly and stack indicates
that it is crashing in the following code:
browser_accessibility_manager.cc:
bool success = false;
if (members->render_widget_host_->process() &&
members->render_widget_host_->process()->channel()) {
// Necessary for the send to keep the UI responsive.
msg->EnableMessagePumping();
success = members->render_widget_host_->process()->channel()->
SendWithTimeout(msg, kAccessibilityMessageTimeOut);
}
it is crashing on the SendWithTimeout() call, because it is called on a
NULL channel.
That does not make any sense since we are testing for NULL channel just
above.
And the channel of the process is only accessed from the UI thread, so this
cannot be a race on channel.
Ananta suggested may be the stack is wrong (and the register values of the
mini-dump) and somehow the crash happens in
SendWithTimeout, but we were not able to repro by trying to kill the
renderer while waiting for the message in SendWithTimeout.
--
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 [email protected]
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
-~----------~----~----~----~------~----~------~--~---
