Open
Bug 1615486
Opened 6 years ago
Updated 9 months ago
Optimization to rely on WeakMap key delegate's previously set gray color
Categories
(Core :: JavaScript: GC, enhancement, P3)
Core
JavaScript: GC
Tracking
()
ASSIGNED
People
(Reporter: sfink, Assigned: sfink)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
As Jon suggested, a delegate that is currently marked gray in a previous GC can be safely considered to still be gray because of read barriers.
Assignee | ||
Comment 1•6 years ago
|
||
Comment 2•6 years ago
|
||
(And not just delegates - anything marked gray in a zone we're not collecting can be considered gray).
Assignee | ||
Comment 3•6 years ago
|
||
(In reply to Jon Coppeard (:jonco) from comment #2)
(And not just delegates - anything marked gray in a zone we're not collecting can be considered gray).
Darn, I didn't read this before figuring it out myself.
Updated•3 years ago
|
Severity: normal → S3
Updated•9 months ago
|
Blocks: GC.performance
Severity: S3 → N/A
You need to log in
before you can comment on or make changes to this bug.
Description
•