Comment #1 on issue 15513 by [email protected]: Reliability failure ntdll!RtlEnterCriticalSection+0xb http://code.google.com/p/chromium/issues/detail?id=15513
My current theory is that some consumer of URLRequestContext is lingering on way too long. This lingerer augments the lifespan of the global HostResolver past the destruction of the IO loop. Since a reference is still held, the HostResolver does not get destroyed; therefore its outstanding jobs do not get cancelled. So when the jobs do finish, they try to post to the already destroyed IO message loop. -- 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 -~----------~----~----~----~------~----~------~--~---
