Comment #4 on issue 21835 by [email protected]: Browser Crash in MessagePumpLibevent::WatchFileDescriptor http://code.google.com/p/chromium/issues/detail?id=21835
Yeah, it is using the member directly not the accessor, so that codepath shouldn't be possible. The only other thing I can think is if something quirky is going on during Thread::Stop(), since that is the other major piece of code which will be run by the destructor when calling io_thread_.reset(). But even if something crazy was happening in Thread::Stop() causing the cleanup (IOThread::CleanUp()) to get run on the main thread, I still can't explain how it would reach io_thread() in order to end up calling CreateIOThread(). Moreover, I would expect more stack frames between ResetIOThread() and CreateIOThread(), since at the very least Thread::Stop() is not inlined. -- 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 -~----------~----~----~----~------~----~------~--~---
