Open Bug 1154000 Opened 10 years ago Updated 3 years ago

Split off another iGC slice if background thread is not ready

Categories

(Core :: JavaScript: GC, defect)

defect

Tracking

()

People

(Reporter: sfink, Unassigned)

References

(Blocks 1 open bug)

Details

One of my GCs spent 73ms waiting for the background thread before continuing on to spend a bunch more time in the last slice of an incremental GC. It would be better if it had waited for the budgeted amount, then given up and returned to the mutator to try again. Related: even if waiting for the background thread doesn't consume the whole budget, it would probably still be better to queue up a separate slice if it takes more than a couple of ms.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.