Closed Bug 1231787 Opened 9 years ago Closed 7 years ago

Integrate memory profiler's gc malloc counter instrumentation with allocations view

Categories

(DevTools :: Performance Tools (Profiler/Timeline), defect, P3)

Product:
DevTools
Component:
Performance Tools (Profiler/Timeline)
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: fitzgen, Unassigned)

Details

I think we can replace the Debugger.Memory's allocations log with the memory profiler's allocations log. It doesn't have ctor names, but we don't use those anyways. What it does have is stacks and more complete coverage of allocations that put pressure on the gc and trigger collections. That coverage is very valuable.
Triaging. Filter on ADRENOCORTICOTROPIC (yes).
Priority: -- → P3
fitzgen: Can you tell me your 2017 thoughts on this bug?
Flags: needinfo?(nfitzgerald)
Close. The memory profile (which I'm not even sure if it exists anymore) doesn't (didn't?) allow breaking down on a custom per-global basis like `Debugger` does, so it can't really be used.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(nfitzgerald)
Resolution: --- → INVALID
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.