Bug 538918 - Don't test the stack depth on entering WaitForNotify(). r=cjones.
authorJim Mathies <jmathies@mozilla.com>
Wed, 10 Feb 2010 20:30:21 -0600
changeset 46657 5d07e1c651f4e0debd89bd62ee8f536f066c2d1b
parent 46656 109e2d8b095d32f697c06b0e0820a11c1bb1237a
child 46658 e5c03e24fe5858fc9a1cf4935063050a4891a1f7
push id1
push userroot
push dateMon, 20 Oct 2014 17:29:22 +0000
reviewerscjones
bugs538918
milestone1.9.3a2pre
Bug 538918 - Don't test the stack depth on entering WaitForNotify(). r=cjones.
ipc/glue/WindowsMessageLoop.cpp
--- a/ipc/glue/WindowsMessageLoop.cpp
+++ b/ipc/glue/WindowsMessageLoop.cpp
@@ -701,22 +701,16 @@ SyncChannel::WaitForNotify()
   return true;
 }
 
 bool
 RPCChannel::WaitForNotify()
 {
   mMutex.AssertCurrentThreadOwns();
 
-  if (!StackDepth()) {
-    NS_ASSERTION(!StackDepth(),
-        "StackDepth() is 0 in a call to RPCChannel::WaitForNotify?");
-    return true;
-  }
-
   MutexAutoUnlock unlock(mMutex);
 
   // Initialize global objects used in deferred messaging.
   Init();
 
   // IsSpinLoopActive indicates modal UI is being displayed in a plugin. Drop
   // down into the spin loop until all modal loops end. If SpinInternalEventLoop
   // returns true, the out-call response we were waiting on arrived, or we