Closed Bug 779073 Opened 13 years ago Closed 13 years ago

"Assertion failure: any" with verifyprebarriers()

Categories

(Core :: JavaScript Engine, defect)

x86_64
macOS
defect
Not set
critical

Tracking

()

RESOLVED FIXED
mozilla18

People

(Reporter: jruderman, Assigned: billm)

Details

(Keywords: assertion, testcase, Whiteboard: [js:t])

Attachments

(2 files)

Attached file testcase
The testcase requires https://www.squarefree.com/extensions/domFuzzLite3.xpi Assertion failure: any, at js/src/jsgc.cpp:3716
Whiteboard: [js:t]
Assignee: general → wmccloskey
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.
Attached patch patchSplinter Review
This fixes the problem.
Attachment #664585 - Flags: review?(terrence)
Comment on attachment 664585 [details] [diff] [review] patch Review of attachment 664585 [details] [diff] [review]: ----------------------------------------------------------------- Nice.
Attachment #664585 - Flags: review?(terrence) → review+
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.

Attachment

General

Creator:
Created:
Updated:
Size: