Updates:
Labels: -Pri-2 -OS-All -Area-Misc Pri-1 OS-Windows Area-BrowserBackend
Comment #1 on issue 8029 by [email protected]: DCHECK hit in ObjectWatcher
from IPC::Logging
http://code.google.com/p/chromium/issues/detail?id=8029
The bots are consistently hitting this bug in ui_tests --single-process
mode.
Is easy to repro. Start with single process mode, create 34 tabs and then
with the
wrench menu select "exit". Call stack is exactly the same:
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++
We hit this DCHECK:
ObjectWatcher::StopWatching() {
DCHECK(watch_->origin_loop == MessageLoop::current());
}
That comes from :
void WaitableEventWatcher::StopWatching() {
watcher_.StopWatching();
}
Note that watch_->origin_loop reports as its thread "Chrome_ChildThread"
and the
current thread is "Chromium_BrowserMain". The original thread is not
present at the
point of DCHECK. This makes sense because the
AtExitManager::ProcessCallbacks happens
very late in the game and always in the main thread.
--
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
-~----------~----~----~----~------~----~------~--~---
