2.2 Gib :(

Chris Coulson chrisccoulson at ubuntu.com
Fri Feb 22 16:38:04 UTC 2013


On 21/02/13 12:21, Ludovic Hirlimann wrote:
> On 2/20/13 6:42 PM, Mike Conley wrote:
>> The output of about:memory (going to Troubleshooting Information,
>> about:memory) is sometimes useful for these things.
>>
> I'm getting 1,780.58 MB (100.0%) -- explicit
> ├──1,685.53 MB (94.66%) ── heap-unclassified
>
> meaning we probably need a few more probes to be able to analyse , right ?
>
> ├─────52.61 MB (02.95%) -- js-non-window
> │ ├──34.21 MB (01.92%) -- compartments
> │ │ ├──31.35 MB (01.76%) ++ non-window-global
> │ │ └───2.86 MB (00.16%) ++ no-global
> │ └──18.40 MB (01.03%) ++ (2 tiny)
> ├─────27.84 MB (01.56%) ++ window-objects
> └─────14.60 MB (00.82%) ++ (16 tiny)
>
> Ludo
>
>
>
> _______________________________________________
> tb-planning mailing list
> tb-planning at mozilla.org
> https://mail.mozilla.org/listinfo/tb-planning
Hi,

I checked today and I'm seeing pretty much the same behaviour as Ludo (> 
2GB, mostly heap-unclassified). I just made a --disable-jemalloc build 
locally and ran it in valgrind, and whilst it's pretty difficult to 
separate real leaks from stuff that just isn't cleaned up properly at 
shutdown, https://bugzilla.mozilla.org/show_bug.cgi?id=844148 did jump 
out to me fairly quickly (although I'm not sure how much it's worth in 
the real world yet).

Regards
Chris



More information about the tb-planning mailing list