1109397 - Find and kill the heap-unclassified leak in my session

Status: RESOLVED WORKSFORME

(Core :: JavaScript: GC, defect)

Description

[Terrence Cole [:terrence]]

Filing a bug for myself since I keep forgetting to investigate.

Comment 1

[Nicholas Nethercote [inactive]]

DMD instructions are at https://developer.mozilla.org/en-US/docs/Mozilla/Performance/DMD :)

Comment 2

[Nicholas Nethercote [inactive]]

> DMD instructions are at
> https://developer.mozilla.org/en-US/docs/Mozilla/Performance/DMD :)

But note that I *just* landed some changes to inbound that change how DMD works (specifically, adding the notion of "modes"). I've updated the docs accordingly, so if you have an older build you'll find those instruction slightly out-of-date... just run with defaults in place and everything should work ok for your use case.

Comment 3

[Terrence Cole [:terrence]]

Attachment: unreported.txt

I tried this out on a brand new session: ~500MiB with 120MiB dark matter. About 20% appears to be gecko profiler. Unfortunately after that it's a /very/ long tail of smallish allocations. I'm thinking that the gecko profiler allocations are probably not the real culprit here: I suspect that once I've left this session open for a week one of the smaller sites will have ballooned.

Comment 4

[Terrence Cole [:terrence]]

This was indeed the gecko profiler extension. With that plugin disabled I am no longer collecting significant amounts of heap-unclassified -- after a few days it's only 200MiB on a 1.5GiB heap. The OOMs are gone so I'm satisfied.

Comment 5

[Nicholas Nethercote [inactive]]

I filed bug 1112336 for adding memory reporting to the profiler.