807850 - Add a memory reporter for the nsScriptNameSpaceManager

Status: RESOLVED FIXED

(Core :: DOM: Core & HTML, defect)

Description

[Nicholas Nethercote [inactive]]

This is one of the bigger single chunks remaining, and it shows up in every
process on B2G.

Comment 1

[Nicholas Nethercote [inactive]]

Attachment: Add a memory reporter for the nsScriptNameSpaceManager.

Pretty straightforward.  On 64-bit builds it's 153 KiB per process, and
probably a bit less on 32-bit.

Comment 2

[Nicholas Nethercote [inactive]]

> Pretty straightforward.  On 64-bit builds it's 153 KiB per process, and
> probably a bit less on 32-bit.

For the main process that is ~0.5% of the heap, for child processes it's ~1%.

Comment 3

[Nicholas Nethercote [inactive]]

https://hg.mozilla.org/integration/mozilla-inbound/rev/5a5775d8c498

Comment 4

[Nicholas Nethercote [inactive]]

Comment on attachment 677608 [details] [diff] [review]
Add a memory reporter for the nsScriptNameSpaceManager.

[Approval Request Comment]

Bug caused by (feature/regressing bug #):  N/A.

User impact if declined:  less understanding of B2G memory consumption.

Testing completed (on m-c, etc.):  just landed on m-c.

Risk to taking this patch (and alternatives if risky):  minimal.  Code is only run when viewing about:memory or triggering a memory report dump.

String or UUID changes made by this patch:  none.

Comment 5

[Ed Morley [:emorley]]

https://hg.mozilla.org/mozilla-central/rev/5a5775d8c498

Comment 6

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/releases/mozilla-aurora/rev/8ae22fe748fc

Comment 7

[Mihai Morar, (:MihaiMorar)]

Can someone please attach a testcase ?