Open Bug 961331 (memory-platform) Opened 6 years ago Updated Last year

[meta] Memory Tool Platform Work

Categories

(DevTools :: Memory, defect, P5)

defect

Tracking

(Not tracked)

People

(Reporter: jimb, Unassigned)

References

(Depends on 27 open bugs)

Details

(Keywords: meta)

Debugger should provide an API for analyzing heap usage and catching leaks. This should include:

- ways to find paths by which objects are retained

- ways to compute objects' retained sizes, and identify the largest N objects in each category

- ways to take a census of the heap and count the numbers (and sizes) of objects in various categories

- ways to take complete, serializable snapshots of the heap, and examine them (almost) as if they were live.
There is IterateZonesCompartmentsArenasCells(), which lets you iterate over the heap. It could be the basis for the 3rd and 4th items in comment 0. The 1st and 2nd items in that comment will need something more like JSTracer.
Depends on: 1012456
Component: JavaScript Engine → Developer Tools: Memory
Product: Core → Firefox
Summary: [jsdbg2] Debugger should provide an API for heap / memory analysis → [meta] DevTools platform APIs for heap / memory analysis
Alias: devtools-memory-apis
Blocks: 1149755
Depends on: 1182699
Alias: devtools-memory-apis → memory-platform
Summary: [meta] DevTools platform APIs for heap / memory analysis → [meta] Memory Tool Platform Work
Has STR: --- → irrelevant
P5 cause this is a meta-bug and blockers will have their own priority that better reflects their individual reality.
Priority: -- → P5
Product: Firefox → DevTools
Depends on: 1474383
See Also: → heapprof
You need to log in before you can comment on or make changes to this bug.