Comment #3 on issue 6500 by [email protected]: Chrome: Crash Report - Stack  
Signature: DebugUtil::BreakDebugger()-77D5E4
http://code.google.com/p/chromium/issues/detail?id=6500

Good news: although this CHECK failure disappeared in 2.0.158.0-qemu,
it reappeared in 2.0.159.0-qemu!  An example is
http://crash-staging/reportdetail?reportid=2c6be6a262ef889f&product=Chrome&version=2.0.159.0-qemu&date=&signature=DebugUtil%3A%3ABreakDebugger()-AA734A

Thread 8 *CRASHED* (EXCEPTION_BREAKPOINT @0x029abce9)
0x029abce9      [chrome.dll     - debug_util_win.cc:102]         
DebugUtil::BreakDebugger()
0x0265188c      [chrome.dll     - logging_chrome.cc:40]         
SilentRuntimeAssertHandler
0x0299e69a      [chrome.dll     - logging.cc:498]        
logging::LogMessage::~LogMessage()
0x02803319      [chrome.dll     - tcp_client_socket_win.cc:235]
net::TCPClientSocket::Write(char const *,int,CallbackRunner<Tuple1<int> > *)
0x027f8422      [chrome.dll     - http_network_transaction.cc:573]
net::HttpNetworkTransaction::DoWriteHeaders()
0x027f7b72      [chrome.dll     - http_network_transaction.cc:348]
net::HttpNetworkTransaction::DoLoop(int)
0x027f76f7      [chrome.dll     - http_network_transaction.cc:287]
net::HttpNetworkTransaction::OnIOComplete(int)
0x0272dbee      [chrome.dll     - task.h:573]   
CallbackImpl<HistoryHandler,void (
HistoryHandler::*)(Value const *),Tuple1<Value const *>  
>::RunWithParams(Tuple1<Value
const *> const &)
0x028034d5      [chrome.dll     - tcp_client_socket_win.cc:316]
net::TCPClientSocket::DoCallback(int)
0x028035cc      [chrome.dll     - tcp_client_socket_win.cc:354]
net::TCPClientSocket::DidCompleteConnect()
0x028036be      [chrome.dll     - tcp_client_socket_win.cc:376]
net::TCPClientSocket::OnObjectSignaled(void *)
0x029af786      [chrome.dll     - object_watcher.cc:30]          
base::ObjectWatcher::Watch::Run()
0x029a37ff      [chrome.dll     - message_loop.cc:308]  
MessageLoop::RunTask(Task  
*)
0x029a3836      [chrome.dll     - message_loop.cc:316]
MessageLoop::DeferOrRunPendingTask(MessageLoop::PendingTask const &)
0x029a39c4      [chrome.dll     - message_loop.cc:408]  MessageLoop::DoWork()
0x029ba865      [chrome.dll     - message_pump_win.cc:468]       
base::MessagePumpForIO::DoRunLoop()
0x029ba389      [chrome.dll     - message_pump_win.cc:52]
base::MessagePumpWin::RunWithDispatcher(base::MessagePump::Delegate
*,base::MessagePumpWin::Dispatcher *)
0x029ba23c      [chrome.dll     - message_pump_win.h:78]
base::MessagePumpWin::Run(base::MessagePump::Delegate *)
0x029a36c9      [chrome.dll     - message_loop.cc:197]  
MessageLoop::RunInternal()
0x029a3696      [chrome.dll     - message_loop.cc:180]  
MessageLoop::RunHandler()
0x029a3639      [chrome.dll     - message_loop.cc:154]  MessageLoop::Run()
0x029a5b73      [chrome.dll     - thread.cc:153]        
base::Thread::ThreadMain()
0x029a4f18      [chrome.dll     - platform_thread_win.cc:26]    `anonymous
namespace'::ThreadFunc(void *)
0x7c80b682      [kernel32.dll   + 0x0000b682]   BaseThreadStart

The relevant source code in tcp_client_socket_win.cc is:

   DWORD num;
   int rv = WSASend(socket_, &buffer_, 1, &num, 0, &overlapped_, NULL);
   if (rv == 0) {
     // TODO(wtc): These temporary CHECKs are intended to determine the  
return
     // value and error code of the WaitForSingleObject call if it doesn't
     // return the expected WAIT_OBJECT_0.  See http://crbug.com/6500.
     DWORD wait_rv = WaitForSingleObject(overlapped_.hEvent, 0);
     if (wait_rv != WAIT_OBJECT_0) {
       if (wait_rv == WAIT_ABANDONED) {
         CHECK(false);
       } else if (wait_rv == WAIT_TIMEOUT) {
         CHECK(false);
       } else if (wait_rv == WAIT_FAILED) {
         DWORD wait_error = GetLastError();
         if (wait_error == ERROR_INVALID_HANDLE) {
           CHECK(false);
         } else {
           CHECK(false);
         }
       } else {
         CHECK(false);  <=== FAILED
       }
     }

It is the last CHECK that failed, which means the return value
of WaitForSingleObject is not any of the documented values
(WAIT_OBJECT_0, WAIT_ABANDONED, WAIT_TIMEOUT, WAIT_FAILED).
I will examine the full memory dump to see if I can find
out what the return value is.

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

Reply via email to