Closed
Bug 704592
Opened 13 years ago
Closed 13 years ago
Assertion failure: thing->compartment()->rt == trc->runtime, at jsgcmark.cpp:118 with JS shell workers
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
People
(Reporter: decoder, Assigned: dmandelin)
Details
(Keywords: assertion, testcase, Whiteboard: js-triage-needed)
Attachments
(1 file)
874 bytes,
application/x-compressed-tar
|
Details |
The attached test asserts on mozilla-central revision 5ebeef1eabcb (options -m -n -a, threadsafe build). The test uses JS shell workers, but I cannot really tell if this is a shell only issue. Flagging S-s due to GC relatedness until triaged.
Comment 1•13 years ago
|
||
If this also happens in the client with web workers then this would be [sg:critical]. If it's strictly a js shell bug then it wouldn't be.
Whiteboard: js-triage-needed → [sg:critical] js-triage-needed
Assignee | ||
Updated•13 years ago
|
Assignee: general → dmandelin
Updated•13 years ago
|
status-firefox10:
--- → affected
status-firefox11:
--- → affected
status-firefox8:
--- → wontfix
status-firefox9:
--- → wontfix
tracking-firefox10:
--- → +
tracking-firefox11:
--- → +
tracking-firefox8:
--- → -
tracking-firefox9:
--- → -
Assignee | ||
Updated•13 years ago
|
Group: core-security
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Comment 3•13 years ago
|
||
Apparently the original bug was filed with the patch for bug 704478 applied, so it's not necessarily a dup.
Group: core-security
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Assignee | ||
Comment 4•13 years ago
|
||
This WFM in a current m-i build. Could you retest it?
Reporter | ||
Comment 5•13 years ago
|
||
Confirmed WFM on m-c 3bf9653c4e46. Is there any more investigation needed?
Assignee | ||
Comment 6•13 years ago
|
||
I think we're good.
Group: core-security
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → WORKSFORME
Updated•13 years ago
|
Whiteboard: [sg:critical] js-triage-needed → js-triage-needed
Updated•13 years ago
|
status-firefox10:
affected → ---
status-firefox11:
affected → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•