Open Bug 1163663 Opened 9 years ago Updated 1 year ago

Assert that the GC is not run during a CC in unexpected places

Categories

(Core :: Cycle Collector, defect)

Product:
Core
Component:
Cycle Collector
Type:
defect

Tracking

()

Tracking Flags:
Tracking Status
firefox41 --- affected

People

(Reporter: mccr8, Unassigned)

Details

The GC should not be run during the CC, from the part in BeginCollection where we trace JS roots, up through ScanRoots.  Running GC during Unlink probably is okay.

Jon said there are a few RAII classes we could use to detect this: "AutoAssertOnGC - asserts if we GC
AutoAssertNoAlloc - asserts if we could possibly GC, even if we don't
AutoCheckCannotGC - asserts if we GC, and makes the analysis check too"

AutoAssertNoAlloc is probably what we want.
Severity: normal → S3
Component: XPCOM → Cycle Collector
You need to log in before you can comment on or make changes to this bug.