Open Bug 1156900 Opened 10 years ago Updated 24 days ago

Because JSGC_MODE_GLOBAL, testing function gc(someObject) always schedules every zone for GC

Categories

(Core :: JavaScript Engine, defect, P3)

defect

Tracking

()

People

(Reporter: fitzgen, Unassigned)

References

(Blocks 2 open bugs)

Details

Spin off from bug 1150253 gc(someObject) is supposed to only GC the given object's zone (and any other zones that happen to be scheduled already) but because of JSGC_MODE_GLOBAL, every zone gets scheduled for GC by GCRuntime::scanZonesBeforeGC. This only became a problem for me when I ported jit-tests to xpcshell-tests. Maybe they have different JSGC_MODEs? I tried setting JSGC_MODE_WHATEVER depending on if an argument was passed to the gc testing function, but that causes a bunch of existing jit-tests to fail. It sure does render the gc testing function less useful, though.
Severity: normal → S3
Priority: -- → P3

(This needs more testing)

You need to log in before you can comment on or make changes to this bug.