Updates:
Cc: [email protected] [email protected]
Labels: -OS-All OS-Windows
Comment #2 on issue 6331 by [email protected]: Chrome: Crash Report - Stack
Signature: logging::LogMessage::~LogMessage()
http://code.google.com/p/chromium/issues/detail?id=6331
I didn't look at the minidumps or full memory dumps. Just
looking at the call stack, I can tell that the following
events occurred:
Hostname resolution completed
We called and stayed in HttpNetworkTransaction::DoLoop
We're in HttpNetworkTransaction::DoWriteHeaders,
which implied the intermediate HttpNetworkTransaction::DoConnect
call must have succeeded synchronously
The CHECK that failed means when TCPClientSocket::Write tried
to send the headers, the event object was already signaled.
So I think what went wrong was that when connect() succeeded
synchronously, we didn't reset the event object and left it
in the signaled 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
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
