Open Bug 1268289 Opened 8 years ago Updated 2 years ago

Memory tools don't give very useful results when profiling Treeherder

Categories

(DevTools :: Memory, defect, P3)

defect

Tracking

(Not tracked)

People

(Reporter: wlach, Unassigned)

References

Details

Attachments

(1 file)

I was profiling memory consumption for treeherder in bug 1267102, and found the devtools memory tool pretty lacking compared to Chrome's. In particular, Chrome gave a detailed summary for exactly which heap-allocated object was taking up a ton of space (ThJobModel) while Firefox's profiler (as far as I could tell) could only vaguely talk about "strings" and "objects".

It seems like the Firefox memory profiler is mostly just exposing stuff on the platform level, without any annotation.

I'm guessing you're already aware of this but I figured I'd file just in case you weren't.
Summary: Memory tools doesn't give very useful results when profiling Treeherder → Memory tools don't give very useful results when profiling Treeherder
Did you try using the allocations stack recording and grouping items by allocation site? Did you investigate individuals and their retaining paths?

We also have the object's constructor's name at the JS::ubi::Node level, but we don't shepherd this through snapshots and back out again.

In general, work on the memory tool has halted for the time being, as the whole devtools team is focused on preparing for a pure html/non-xul world.
I guess P2? Not clear to me what concrete action items we have here. Just the object constructor names?
Priority: -- → P2
Blocks: 1112352
Product: Firefox → DevTools
See Also: → heapprof
Priority: P2 → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: