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

1 files changed, 5 insertions, 4 deletions

diff --git a/base/message_loop.h b/base/message_loop.h
index 1610d07..8d5644329 100644
--- a/base/message_loop.h
+++ b/base/message_loop.h
@@ -353,7 +353,8 @@ class MessageLoop {
           quit_now_(loop->quit_now_),
           quit_received_(loop->quit_received_),
           run_depth_(loop->run_depth_) {
-      loop->quit_now_ = loop->quit_received_ = false;
+      loop->quit_now_ = false;
+      loop->quit_received_ = 0;
       ++loop->run_depth_;
     }
 
@@ -368,7 +369,7 @@ class MessageLoop {
     MessageLoop* loop_;
     Dispatcher* dispatcher_;
     bool quit_now_;
-    bool quit_received_;
+    int quit_received_;
     int run_depth_;
   };  // struct ScopedStateSave
 
@@ -586,8 +587,8 @@ class MessageLoop {
   bool exception_restoration_;
 
   Dispatcher* dispatcher_;
-  bool quit_received_;
-  bool quit_now_;
+  int quit_received_;  // The number of kQuitMsg's processed during run.
+  bool quit_now_;  // A dispatcher indicated the message pump should terminate.
 
   std::string thread_name_;
   // A profiling histogram showing the counts of various messages and events.