Closed
Bug 878120
Opened 11 years ago
Closed 10 years ago
[meta] GC: Call JS_IsAboutToBeFinalized on weak CC participant edges
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
DUPLICATE
of bug 650161
People
(Reporter: terrence, Unassigned)
References
(Blocks 1 open bug)
Details
No description provided.
Reporter | ||
Updated•10 years ago
|
Reporter | ||
Comment 1•10 years ago
|
||
Regarding the purpose of this bug, which I should have expanded upon when filing initially: for moving GC, we must tell the GC about all edges in every GC. Older code in SpiderMonkey was in the habit of not marking some edges when another edge was known to have been marked. If we do this now, however, we'll end up not updating a moved edge. At this point, we're fairly certain we have verified that we mark all strong and weak edges in SpiderMonkey and all strong edges in Gecko. I don't think there is a specific problem with Gecko not tracing some weak edges, but I want to dive into the weakmap marking code in gecko and verify manually anyway. Just haven't had time yet.
Assignee | ||
Updated•10 years ago
|
Assignee: general → nobody
Reporter | ||
Comment 2•10 years ago
|
||
This getting done naturally as part of the shakeout in getting compacting GC operational.
You need to log in
before you can comment on or make changes to this bug.
Description
•