Closed
Bug 1597999
Opened 5 years ago
Closed 5 years ago
Allow retrieving NodeId for a given JS Object
Categories
(Core :: JavaScript Engine, enhancement, P3)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla72
| Tracking | Status | |
|---|---|---|
| firefox72 | --- | fixed |
People
(Reporter: ochameau, Assigned: ochameau)
References
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
This allows identifying a particular object when using the HeapSnapshot API.
HeapSnapshot.computeDominatorTree() returns a tree of objects, but there is no way to identify a given JS object in it.
Getting the node id of a given JS object helps you browse this tree from a given object you know is being leaked. Or just check if it is leaked at all.
|
Assignee | |
Comment 1•5 years ago
|
||
This helps retrieving the NodeId for any JS Object you pass in.
This allows identifying a particular object when using HeapSnapshot API.
HeapSnapshot.computeDominatorTree() returns a tree of object,
but there is no way to identify a given JS object in it.
Getting the node id of a given JS object helps you browse this tree
from a given object you know is leaking.
|
||
Updated•5 years ago
|
Priority: -- → P3
Pushed by apoirot@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/82b716f10a12
Implements ChromeUtils.getObjectNodeId. r=jimb
|
||
Comment 3•5 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox72:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla72
You need to log in
before you can comment on or make changes to this bug.
Description
•