Comment #7 on issue 9258 by [email protected]: Review the two WaitForSingleObject(INFINITE) calls in tcp_client_socket_win.cc http://code.google.com/p/chromium/issues/detail?id=9258
Nicolas said that we're hanging in the WaitForSingleObject call in TCPClientSocket::Disconnect(). That call is more problematic. We can move that call to a thread in the thread pool so that the IO thread doesn't block. This requires changing the ClientSocket interface to use the reference-counted IOBuffer class, so that the TCPClientSocket destructor can hand over its reference to the IOBuffer to the thread pool. We must realize that this merely make the WaitForSingleObject call hang another thread in the thread pool. If the hang never finishes, we could potentially accumulate a lot of threads blocking in these WaitForSingleObject calls. So we should spend some time understanding why these WaitForSingleObject calls hang, and finding out whether they hang forever or for a finite time. -- 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 -~----------~----~----~----~------~----~------~--~---
