Comment #5 on issue 21835 by [email protected]: Browser Crash in MessagePumpLibevent::WatchFileDescriptor http://code.google.com/p/chromium/issues/detail?id=21835
OK, this is just the optimizer getting cute. There must be a little bit of reordering going on. Some of the function names that show up are just from adjacent functions. The main thread stack is really: pthread_join from libSystem.B.dylib PlatformThread::Join(_opaque_pthread_t*) platform_thread_posix.cc:119 base::Thread::Stop() thread.cc:114 (anonymous namespace)::IOThread::~IOThread() browser_process_impl.cc:103 BrowserProcessImpl::ResetIOThread() browser_process_impl.cc:340 BrowserProcessImpl::~BrowserProcessImpl() browser_process_impl.cc:207 browser_shutdown::Shutdown() browser_shutdown.cc:138 BrowserMain(MainFunctionParams const&) browser_main.cc:847 ChromeMain chrome_dll_main.cc:603 main chrome_exe_main.mm:17 which looks fine. -- 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 -~----------~----~----~----~------~----~------~--~---
