Updates:
Cc: [email protected] [email protected] [email protected]
[email protected]
Labels: -Pri-2 -Area-Misc Pri-1 Area-WebKit ReleaseBlock-Dev
Comment #2 on issue 17710 by [email protected]: New crash in reliability
tests
http://code.google.com/p/chromium/issues/detail?id=17710
It's hard to tell what else might have happened within
IPC::SyncChannel::SendWithTimeout, but it seems likely that the Frame may
have been
destroyed during the nested MessageLoop in SendWithTimeout. I think
WebCore has code
to keep frames alive until we return to the message loop, but that code
probably really
wants to defer destruction until the topmost message loop. If we could
arrange for
something like that to happen, it might help here.
--
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
-~----------~----~----~----~------~----~------~--~---
