Closed Bug 807850 Opened 8 years ago Closed 8 years ago

Add a memory reporter for the nsScriptNameSpaceManager

Categories

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

Product:
Core
Component:
DOM: Core & HTML
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla19
Tracking Flags:
Tracking Status
firefox18 --- fixed
firefox19 --- fixed

People

(Reporter: njn, Assigned: njn)

References

Details

(Whiteboard: [MemShrink])

Attachments

(1 file)

Add a memory reporter for the nsScriptNameSpaceManager.
6.57 KB, patch
jst
: review+
bajaj
: approval-mozilla-aurora+
Details | Diff | Splinter Review 
This is one of the bigger single chunks remaining, and it shows up in every
process on B2G.
Pretty straightforward.  On 64-bit builds it's 153 KiB per process, and
probably a bit less on 32-bit.
Attachment #677608 - Flags: review?(jst)
Blocks: B2GDarkMatter
Whiteboard: [MemShrink]
> 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%.
Attachment #677608 - Flags: review?(jst) → review+
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.
Attachment #677608 - Flags: approval-mozilla-aurora?
https://hg.mozilla.org/mozilla-central/rev/5a5775d8c498
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla19
Attachment #677608 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Can someone please attach a testcase ?
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.