Comment out the xpc_DumpJSStack call for now, since it causes fatal JS_Asserts. (Bug 510489) a=bustage
authorL. David Baron <dbaron@dbaron.org>
Thu, 09 Dec 2010 21:35:00 -0800
changeset 59064 6986bf97d8b4e1762160c05d0be96b74a24a79a2
parent 59063 9103bd2267e78d3ea1b3524417f1c199c45f86dc
child 59065 a5bbcbc3bd3251269489f9c10a5bcb750d77e43e
push id1
push usershaver@mozilla.com
push dateTue, 04 Jan 2011 17:58:04 +0000
reviewersbustage
bugs510489
milestone2.0b8pre
Comment out the xpc_DumpJSStack call for now, since it causes fatal JS_Asserts. (Bug 510489) a=bustage
js/src/xpconnect/src/xpcwrappednativescope.cpp
--- a/js/src/xpconnect/src/xpcwrappednativescope.cpp
+++ b/js/src/xpconnect/src/xpcwrappednativescope.cpp
@@ -774,18 +774,22 @@ void DEBUG_CheckForComponentsInScope(JSC
 
     // This is pretty much always bad. It usually means that native code is
     // making a callback to an interface implemented in JavaScript, but the
     // document where the JS object was created has already been cleared and the
     // global properties of that document's window are *gone*. Generally this
     // indicates a problem that should be addressed in the design and use of the
     // callback code.
     NS_ERROR("XPConnect is being called on a scope without a 'Components' property!  (stack and details follow)");
+    // Dumping the JS stack causes fatal JS asserts in some cases, so
+    // comment it out for now.
+#if 0
     printf("The current JS stack is:\n");
     xpc_DumpJSStack(cx, JS_TRUE, JS_TRUE, JS_TRUE);
+#endif
 
     printf("And the object whose scope lacks a 'Components' property is:\n");
     js_DumpObject(startingObj);
 
     JSObject *p = startingObj;
     while(p->isWrapper())
     {
         p = p->getProxyPrivate().toObjectOrNull();