Closed Bug 653033 Opened 14 years ago Closed 13 years ago

"Assertion failure: cx->isExceptionPending()" with proxies, typed arrays, OOM

Categories

(Core :: JavaScript Engine, defect)

x86_64
macOS
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jruderman, Unassigned)

Details

(Keywords: assertion, testcase)

Attachments

(2 files)

Assertion failure: cx->isExceptionPending(), at js/src/jsscan.cpp:1931
Attached file stack trace
This appears to be an OOM crash. I got a different stack trace from what you got: I got a compartment assert via trying to call JS_GetParent as part of reporting an OOM error: nsIScriptGlobalObject * nsJSUtils::GetStaticScriptGlobal(JSContext* aContext, JSObject* aObj) { nsISupports* supports; JSClass* clazz; JSObject* parent; JSObject* glob = aObj; // starting point for search if (!glob) return nsnull; while ((parent = ::JS_GetParent(aContext, glob))) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ compartment assert here glob = parent; glob is a BackstagePass, and we get here from running chrome JS. That seems like some kind of good hint, but I don't know what it means.
WFM on current nightly, also it hangs a little bit. GetStaticScriptGlobal seems to be gone.
Yeah, WFM. I think it makes sense that the testcase hangs for a bit.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Summary: "Assertion failure: cx->isExceptionPending()" with proxies, typed arrays → "Assertion failure: cx->isExceptionPending()" with proxies, typed arrays, OOM
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: