Closed Bug 729008 Opened 9 years ago Closed 9 years ago

Add memory reporter for FramePropertyTable

Categories

(Core :: Layout, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla13

People

(Reporter: n.nethercote, Assigned: n.nethercote)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Attached patch patchSplinter Review
DMD pointed me at FramePropertyTable.  On a workload of 14 wikipedia tabs, the this patch improves coverage of layout memory by about 1.3MB of additional layout memory.

Other minor changes:
- Renamed "layout/styledata" reports as "layout/style-sets".
- |const|-ifies nsTHashTable::SizeOfIncludingThis
Attachment #599048 - Flags: review?(bzbarsky)
Comment on attachment 599048 [details] [diff] [review]
patch

r=me

It's interesting that we're getting 1.3MB of proptable storage but not that much for the values... Might be worth seeing whether we should do some reporting for the values too at some point.
Attachment #599048 - Flags: review?(bzbarsky) → review+
> It's interesting that we're getting 1.3MB of proptable storage but not that
> much for the values... Might be worth seeing whether we should do some
> reporting for the values too at some point.

That's what this comment is about:

+      // We don't need to measure mProperty because it always points to static
+      // memory.  As for mValue:  if it's a single value we can't measure it,
+      // because the type is opaque;  if it's an array, we measure the array
+      // storage, but we can't measure the individual values, again because
+      // their types are opaque.

However, we have mProperty->mDestructor and mProperty->mDestructorWithFrame;  I could add mProperty->mSizeOfIncludingthis...
Yeah, perhaps as a followup if we see those allocations.
https://hg.mozilla.org/mozilla-central/rev/878c5c8b8b21
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla13
You need to log in before you can comment on or make changes to this bug.