Open
Bug 1588127
Opened 5 years ago
Updated 5 months ago
Make it harder to misuse GC hash tables
Categories
(Core :: JavaScript: GC, task, P3)
Core
JavaScript: GC
Tracking
()
NEW
People
(Reporter: jonco, Unassigned)
References
(Blocks 1 open bug)
Details
Following on from bug 1585921, we should document what the correct/recommended barriers are for GC hash tables and then try to enforce this statically as best we can.
|
Reporter | |
Comment 1•5 years ago
|
||
One issue is for atom keys. Previously I think we advised using HeapPtr for these, but now that strings can be nursery allocated these have a post barrier which will execute even though atoms are never nursery allocated. So it works, it's slightly inefficient, but mainly it worries me that we're even considering updating atom keys.
|
|
Reporter | |
Updated•5 years ago
|
Priority: -- → P2
|
||
Updated•2 years ago
|
Severity: normal normal → S3 S3
|
||
Updated•5 months ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•