Closed Bug 903732 Opened 12 years ago Closed 12 years ago

Likely leak in nsSVGTextFrame2::SetupInheritablePaint()...

Categories

(Core :: SVG, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla26

People

(Reporter: jst, Assigned: longsonr)

Details

(Whiteboard: [MemShrink])

Attachments

(2 files)

Attached file DMD log snippet.
After having run my browser for quite some time I see ~450 megs of memory in heap-unclassified, ~200 of which seems to be coming from inside nsSVGTextFrame2::SetupInheritablePaint(). I don't understand that code well enough to say much about it off the top of my head, but closing the one webpage that I know uses SVG and updates all the time (real time bandwidth usage graph from a router running tomato) does *not* make this memory be released. Happy to try to help dig in here if the stacks in the attached DMD data isn't enough to know what's going on here. This is Firefox running in a vnc session, so no accelerated anything here.
Attached patch patchSplinter Review
If you apply this patch, does that fix the leak?
Attachment #788497 - Flags: feedback?(jst)
Comment on attachment 788497 [details] [diff] [review] patch It does indeed! Thanks for the fix!
Attachment #788497 - Flags: feedback?(jst) → feedback+
Attachment #788497 - Flags: review?(dholbert)
Also, this reminds me of bug 836173 which was the identical problem in a different spot. I did a quick grep for other occurrences of this same pattern but didn't find any... Others might want to dig in a bit too though, as I only glanced at this myself.
Attachment #788497 - Flags: review?(dholbert) → review+
Assignee: nobody → longsonr
Thanks for fixing my error, Robert. :)
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla26
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: