Comment #7 on issue 6500 by [email protected]: Chrome: Crash Report - Stack Signature: DebugUtil::BreakDebugger()-77D5E4 http://code.google.com/p/chromium/issues/detail?id=6500
The crash reports of 2.0.159.2-qemu are in. I looked at five of the full memory dumps of this crash, and they all have: wait_rv: 0x102 (WAIT_TIMEOUT) wait_error: 0 (meaningful only if wait_rv is WAIT_FAILED) This verified that the event object may not be in the signaled state when WSASend succeeds synchronously (returns 0). With this knowledge, I will proceed to write a patch. -- 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 -~----------~----~----~----~------~----~------~--~---
