diff options
author | jar@google.com <jar@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2008-08-03 20:18:06 +0000 |
---|---|---|
committer | jar@google.com <jar@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2008-08-03 20:18:06 +0000 |
commit | 0ee1cb3b9c148d17b9181164f911fc8b949f6bdc (patch) | |
tree | b1b0f4f165ff8934936a99dbea8458988888f2e5 /base/message_loop.cc | |
parent | 9c56e17844b240a5b87f488b79bd24d852e2cf51 (diff) | |
download | chromium_src-0ee1cb3b9c148d17b9181164f911fc8b949f6bdc.zip chromium_src-0ee1cb3b9c148d17b9181164f911fc8b949f6bdc.tar.gz chromium_src-0ee1cb3b9c148d17b9181164f911fc8b949f6bdc.tar.bz2 |
This is a test, and will rollback asap after a build/test cycle starts.
I use a counter of MessageLoop::Quit() calls so that I can re-post "extra" calls when MessageLoop::Run() terminates. This assures that no quits are lost... but I'm not sure if some code abused the Quit() calls, and already posts many-too-many quits :-/. I want to see if the tree tests go red, and how the distributed reliability test responds.
The test should already pass the basic unit_test and base_unittest, but I'm not sure what the rest of the UI tests etc will do. If I'm lucky, they'll be "less" flakey. ...but they may just go red all over :-(
TBR
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@298 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base/message_loop.cc')
-rw-r--r-- | base/message_loop.cc | 24 |
1 files changed, 13 insertions, 11 deletions
diff --git a/base/message_loop.cc b/base/message_loop.cc index 7d2fbff..aa71d8d 100644 --- a/base/message_loop.cc +++ b/base/message_loop.cc @@ -128,7 +128,7 @@ MessageLoop::MessageLoop() : message_hwnd_(NULL), exception_restoration_(false), nestable_tasks_allowed_(true), dispatcher_(NULL), - quit_received_(false), + quit_received_(0), quit_now_(false), task_pump_message_pending_(false), run_depth_(0) { @@ -226,6 +226,16 @@ void MessageLoop::RunInternal(Dispatcher* dispatcher, bool non_blocking) { // and leave messages pending, so don't assert the above fact). RunTraditional(non_blocking); DCHECK(non_blocking || quit_received_ || quit_now_); + // Repost excess kMsgQuit's that were received before we exit. + int excess_quits = quit_received_ - 1; // One is expected. + if (non_blocking || quit_now_) + ++excess_quits; // Any quit is an excess quit. + if (excess_quits > run_depth_ - 1) { + // DCHECK(false); // Someone sent redundant quits. + excess_quits = run_depth_ - 1; + } + while (--excess_quits >= 0) + Quit(); } void MessageLoop::RunTraditional(bool non_blocking) { @@ -245,6 +255,7 @@ void MessageLoop::RunTraditional(bool non_blocking) { more_work_is_plausible |= ProcessNextDeferredTask(); more_work_is_plausible |= ProcessNextObject(); + more_work_is_plausible |= ProcessNextDelayedNonNestableTask(); if (more_work_is_plausible) continue; @@ -255,11 +266,6 @@ void MessageLoop::RunTraditional(bool non_blocking) { if (ProcessSomeTimers()) continue; - // We run delayed non nestable tasks only after all nestable tasks have - // run, to preserve FIFO ordering. - if (ProcessNextDelayedNonNestableTask()) - continue; - if (non_blocking) return; @@ -398,11 +404,7 @@ LRESULT MessageLoop::MessageWndProc(HWND hwnd, UINT message, } case kMsgQuit: { - // TODO(jar): bug 1300541 The following assert should be used, but - // currently too much code actually triggers the assert, especially in - // tests :-(. - //CHECK(!quit_received_); // Discarding a second quit will cause a hang. - quit_received_ = true; + ++quit_received_; return 0; } } |