Comment #3 on issue 15513 by [email protected]: Reliability failure ntdll!RtlEnterCriticalSection+0xb http://code.google.com/p/chromium/issues/detail?id=15513
Confirmed the theory above -- the outstanding URLRequests are NOT being cancelled during shutdown. In fact the debug log even tells me they are explicitly being leaked: [2356:7008:909610531:WARNING:url_request_job_tracker.cc(18)] Leaking 1 URLRequestJob object(s), this could be because the URLRequest forgot to free it (bad), or if the program was terminated while a request was active (normal). [2356:7008:909610531:WARNING:url_request.cc(479)] Leaking 1 URLRequest object(s) Therefore this URLRequest is holding a reference to the URLRequestContext preventing it from being freed, and also preventing the refcounted HostResolver from being freed. (And by not freeing the HostResolver, we don't cancel the requests in the worker pool before the IO thread is killed by browser shutdown). Will see if this resolves the crashers on chrome-bot... -- 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 -~----------~----~----~----~------~----~------~--~---
