Closed Bug 1062012 Opened 11 years ago Closed 11 years ago

Assertion in FinishAnyCurrentCollection() is too strong

Categories

(Core :: XPCOM, defect)

Product:
Core
Component:
XPCOM
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1087799

People

(Reporter: mccr8, Unassigned)

Details

Kyle hit this. If some code ends up GCing while unlinking, then the GC tries to finish off the current CC, but it can't, because we're reentering the CC, so the CC does nothing. But then the assert at the end of FinishAnyCurrentCollection() gets mad because the CC didn't finish. Technically, it should also be okay if we're past marking. Though if we're running JS in unlink, I suppose it could resurrect some object via a weak reference, and bad things will happen, so maybe we should assert or crash in some other way... hmm.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.