Closed
Bug 779073
Opened 13 years ago
Closed 13 years ago
"Assertion failure: any" with verifyprebarriers()
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
mozilla18
People
(Reporter: jruderman, Assigned: billm)
Details
(Keywords: assertion, testcase, Whiteboard: [js:t])
Attachments
(2 files)
|
49 bytes,
text/html
|
Details | |
|
3.88 KB,
patch
|
terrence
:
review+
|
Details | Diff | Splinter Review |
The testcase requires https://www.squarefree.com/extensions/domFuzzLite3.xpi
Assertion failure: any, at js/src/jsgc.cpp:3716
Updated•13 years ago
|
Whiteboard: [js:t]
| Assignee | ||
Updated•13 years ago
|
Assignee: general → wmccloskey
| Assignee | ||
Comment 1•13 years ago
|
||
This is caused by a bookkeeping problem. During a write barrier verification, we set gcIncrementalState to MARK. Later on, we assume that when that is set, then some compartment must have already been scheduled for incremental GC, which is wrong. I need to decide how to fix this.
| Assignee | ||
Comment 2•13 years ago
|
||
This fixes the problem.
Attachment #664585 -
Flags: review?(terrence)
Comment 3•13 years ago
|
||
Comment on attachment 664585 [details] [diff] [review]
patch
Review of attachment 664585 [details] [diff] [review]:
-----------------------------------------------------------------
Nice.
Attachment #664585 -
Flags: review?(terrence) → review+
| Assignee | ||
Comment 4•13 years ago
|
||
Comment 5•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla18
You need to log in
before you can comment on or make changes to this bug.
Description
•