Closed Bug 875284 Opened 12 years ago Closed 12 years ago

Assertion failure: XPCJSRuntime::Get()->GetJSContextStack()->Peek() == cx, at js/xpconnect/wrappers/WrapperFactory.cpp:396

Categories

(Core :: JavaScript Engine, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: past, Unassigned)

References

Details

(Keywords: assertion)

Attachments

(1 file)

Attached file Crash log
I got this from a debug build on fx-team tip, plus the patches from bug 870081 and its dependencies (but they are all JS code, so presumably unrelated): Assertion failure: XPCJSRuntime::Get()->GetJSContextStack()->Peek() == cx, at js/xpconnect/wrappers/WrapperFactory.cpp:396 I was using the Browser Debugger when the assertion was hit. Crash log attached. Top of the stack: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 xpc::WrapperFactory::Rewrap(JSContext*, JS::Handle<JSObject*>, JS::Handle<JSObject*>, JS::Handle<JSObject*>, JS::Handle<JSObject*>, unsigned int) + 193 (WrapperFactory.cpp:388) 1 JSCompartment::wrap(JSContext*, JS::MutableHandle<JS::Value>, JS::Handle<JSObject*>) + 2278 (jscompartment.cpp:327) 2 js::CrossCompartmentWrapper::call(JSContext*, JS::Handle<JSObject*>, JS::CallArgs const&) + 282 (jswrapper.cpp:441) 3 js::Proxy::call(JSContext*, JS::Handle<JSObject*>, JS::CallArgs const&) + 246 (jsproxy.h:377) 4 proxy_Call(JSContext*, unsigned int, JS::Value*) + 170 (GuardObjects.h:100) 5 js::CallJSNative(JSContext*, int (*)(JSContext*, unsigned int, JS::Value*), JS::CallArgs const&) + 82 (jscntxtinlines.h:346) 6 js::Invoke(JSContext*, JS::CallArgs, js::MaybeConstruct) + 1534 (jsinterp.cpp:401) 7 js::Interpret(JSContext*, js::StackFrame*, js::InterpMode, bool) + 4391 (jsinterp.cpp:2268) 8 js::RunScript(JSContext*, js::StackFrame*) + 1096 (jsinterp.cpp:365) 9 js::Invoke(JSContext*, JS::CallArgs, js::MaybeConstruct) + 1664 (jsinterp.cpp:422)
I found an easy way to trigger this assertion in the latest fx-team tip: 1. Tools -> Web Developer -> Browser Debugger 2. Tools -> Web Developer -> Browser Console 3. Boom.
Another reliable set of STR: 1. Tools -> Web Developer -> Browser Debugger 2. Nightly -> Preferences 3. Boom.
This seems fixed now, but I have no idea which patch did it.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: