Closed
Bug 1701951
Opened 4 years ago
Closed 3 months ago
Record whether a GC slice is running in idle time
Categories
(Core :: JavaScript: GC, enhancement, P3)
Core
JavaScript: GC
Tracking
()
RESOLVED
DUPLICATE
of bug 1752646
People
(Reporter: sfink, Unassigned)
References
(Blocks 1 open bug)
Details
I often infer whether a GC slice is running during idle time by its budget (49ms or close to it is a long idle period; I think 10ms and 5ms are inter-frame idle). It would be better to record it explicitly as a record of the scheduling behavior.
It could perhaps be 3 possibilities: short idle, refresh driver idle, non-idle?
Given how much of GC happens in idle time these days, we could go further and color the non-idle slices differently in the marker view.
Updated•4 years ago
|
Severity: -- → N/A
Priority: -- → P2
Updated•3 months ago
|
Blocks: GC.easeofuse
Priority: P2 → P3
Reporter | ||
Comment 1•3 months ago
|
||
The GC slice markers now describe their budget with "(idle)" in this case. Or "(started idle but extended)".
You need to log in
before you can comment on or make changes to this bug.
Description
•