Closed Bug 781722 Opened 13 years ago Closed 13 years ago

Crash from a scratchpad's sandbox: "Assertion Failure: rt->heapState == JSRuntime::Idle"

Categories

(Core :: XPConnect, defect)

x86_64
Linux
defect
Not set
critical

Tracking

()

RESOLVED FIXED
mozilla17

People

(Reporter: espadrine, Unassigned)

Details

(Keywords: assertion, crash)

Crash Data

Attachments

(2 files)

Backtrace: http://pastebin.mozilla.org/1747828 Situation: writing in the scratchpad that may have evaluated something in the background. I got the following message, too: Assertion failure: rt->heapState == JSRuntime::Idle, at /home/tyl/files/cloud/fx-team/js/src/jsapi.cpp:241
Attached file Backtrace
Severity: normal → critical
Crash Signature: [@ JS_GetGlobalForScopeChain]
Keywords: assertion, crash
Bill, Nick, looks like we're running into an AssertHeapIsIdle assertion while collecting compartment stats. Can you have a look at the stack and say where we're going wrong?
I assume it's reasonable for JS_GetGlobalForScopeChain() to be called within a call to nsXPConnect::GetNativeOfWrapper()? If so, the assertion is too strong, and should be changed to AssertHeapIsIdleOrIterating(). It's possible that we'll see this same overtight assertion in other jsapi.cpp functions that can be called within GetNativeOfWrapper().
Attachment #651240 - Flags: review?(wmccloskey)
Attachment #651240 - Flags: review?(wmccloskey) → review+
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla17
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: