Idle GC slices are usually not interruptible
Categories
(Core :: JavaScript: GC, enhancement, P2)
Tracking
()
People
(Reporter: sfink, Unassigned)
References
(Blocks 1 open bug)
Details
Looking at some GCSlice markers in the profile, I noticed a 5ms interruptible slice and several 100ms non-interruptible slices. That's not good; an idle slice should normally be interruptible so that if a keypress comes in, it'll stop immediately (and it probably wasn't that critical if it was running in idle time).
|
Reporter | |
Comment 1•5 months ago
|
||
I looked at one of my own profiles, and it showed interruptible 49ms idle slices, which squeaks in just under the limit. (If it is 50ms or greater, it will be considered an extended slice, and will not be made interruptible.)
The ones from the profile I was looking at are 100ms, noninterruptible. Hm... but they also aren't annotated as being idle! So I'm no longer sure where the 100ms slices are coming from, and whether it would make sense for them to be interruptible or not.
|
||
Updated•5 months ago
|
Description
•