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

Status: NEW

(DevTools :: Memory, defect, P3)

Description

[William Lachance (:wlach)]

Attachment: Screenshot of profiling treeherder with Chrome (note detailed information on objects)

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.

Comment 1

[Nick Fitzgerald [:fitzgen] [⏰PST; UTC-8]]

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.

Comment 2

[Nick Fitzgerald [:fitzgen] [⏰PST; UTC-8]]

I guess P2? Not clear to me what concrete action items we have here. Just the object constructor names?