Status: Assigned Owner: [email protected] CC: [email protected] Labels: Type-Bug Pri-2 OS-All Area-Misc
New issue 8029 by [email protected]: DCHECK hit in ObjectWatcher from IPC::Logging http://code.google.com/p/chromium/issues/detail?id=8029 I just happened upon this in a tip of tree build when exiting. It isn't always reproducible. Here's the trace: chrome.dll!DebugUtil::BreakDebugger() Line 102 C++ chrome.dll!logging::LogMessage::~LogMessage() Line 509 C++ chrome.dll!base::ObjectWatcher::StopWatching() Line 84 C++ chrome.dll!base::WaitableEventWatcher::StopWatching() Line 44 C++ > chrome.dll!IPC::Logging::~Logging() Line 103 C++ chrome.dll!IPC::Logging::`scalar deleting destructor'() + 0x16 bytes C++ chrome.dll!DefaultSingletonTraits<IPC::Logging>::Delete(IPC::Logging * x=0x046f1a98) Line 26 + 0x22 bytes C++ chrome.dll!Singleton<IPC::Logging,DefaultSingletonTraits<IPC::Logging>,IPC::Logging>::OnExit(vo id * unused=0x00000000) Line 172 + 0x15 bytes C++ chrome.dll!base::AtExitManager::ProcessCallbacksNow() Line 63 + 0x9 bytes C++ chrome.dll!base::AtExitManager::~AtExitManager() Line 34 C++ chrome.dll!ChromeMain(HINSTANCE__ * instance=0x00400000, sandbox::SandboxInterfaceInfo * sandbox_info=0x0012fe88, wchar_t * command_line=0x000209aa) Line 349 + 0x48 bytes C++ chrome.exe!wWinMain(HINSTANCE__ * instance=0x00400000, HINSTANCE__ * prev_instance=0x00000000, wchar_t * command_line=0x000209aa, int __formal=1) Line 103 + 0x12 bytes C++ chrome.exe!__tmainCRTStartup() Line 324 + 0x35 bytes C chrome.exe!wWinMainCRTStartup() Line 196 C kernel32.dll!7c817067() [Frames below may be incorrect and/or missing, no symbols loaded for kernel32.dll] Darin says the key thing is that IPC Logging shutdown occurs AFTER the MessageLoop has been shutdown, which then tries to stop the ObjectWatcher. This is bad because UnregisterWaitEx done by ObjectWatcher may try and post something to the message loop, but the message loop is now dead. The ObjectWatcher owned by IPC Logging needs to be stopped while the MessageLoop is running. -- 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 -~----------~----~----~----~------~----~------~--~---
