Closed
Bug 2020003
Opened 27 days ago
Closed 9 days ago
Add support for weak map edges to nsICycleCollectorListener.idl
Categories
(Core :: Cycle Collector, task)
Core
Cycle Collector
Tracking
()
RESOLVED
FIXED
150 Branch
| Tracking | Status | |
|---|---|---|
| firefox150 | --- | fixed |
People
(Reporter: mccr8, Assigned: florian)
References
Details
Attachments
(1 file)
Eons ago I added support for weak maps to the cycle collector, but I never got around to adding support to nsICycleCollectorListener, which is sort of an experimental interface to get the results of the cycle collection from JS. It hasn't been heavily used, but a few people are exploring using it, so we should implement this.
The implementation of this will have to be in nsCycleCollectorLogger::NoteWeakMapEntry, adding a mWantAfterProcessing case like the other methods.
| Assignee | ||
Comment 1•27 days ago
|
||
nsICycleCollectorHandler now exposes noteWeakMapEntry, allowing JS
consumers to receive weak map entries from the CC graph. This enables
ShutdownLeakPathFinder and CCAnalyzer to find retention paths that
pass through weak maps.
Updated•27 days ago
|
Assignee: nobody → florian
Status: NEW → ASSIGNED
Pushed by fqueze@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/7b92246a72f7
https://hg.mozilla.org/integration/autoland/rev/a7ce9982d1a9
Add weak map edge support to nsICycleCollectorHandler. r=mccr8,devtools-reviewers,ochameau
Status: ASSIGNED → RESOLVED
Closed: 9 days ago
status-firefox150:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 150 Branch
Updated•2 days ago
|
QA Whiteboard: [qa-triage-done-c151/b150]
You need to log in
before you can comment on or make changes to this bug.
Description
•