Closed Bug 405639 Opened 16 years ago Closed 16 years ago

Dynamically created <svg:use> reference loop causes nsGenericElement leak

Categories

(Core :: SVG, defect, P3)

Product:
Core
Component:
SVG
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla1.9beta2

People

(Reporter: jruderman, Assigned: peterv)

References

Details

(Keywords: memory-leak, testcase)

Attachments

(2 files)

testcase
467 bytes, image/svg+xml
Details
v1
1.80 KB, patch
sicking
: review+
sicking
: superreview+
sicking
: approval1.9+
Details | Diff | Splinter Review
Attached image testcase — 
Steps to reproduce:
1. export XPCOM_MEM_LEAK_LOG=2
2. Run a debug build of Firefox.
3. Load the testcase.
4. Quit Firefox.

Result: trace-refcnt reports that several nsGenericElement objects (along with a bunch of others) have leaked.

Bug 376666 might be related.
Attached patch v1 — — Splinter Review 
Unlinking seems safe, mOriginal/mClone/mSourceContent are null-checked before use.
Assignee: nobody → peterv
Status: NEW → ASSIGNED
Attachment #290594 - Flags: superreview?(jonas)
Attachment #290594 - Flags: review?(jonas)
Attachment #290594 - Flags: superreview?(jonas)
Attachment #290594 - Flags: superreview+
Attachment #290594 - Flags: review?(jonas)
Attachment #290594 - Flags: review+
Attachment #290594 - Flags: approval1.9+
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Flags: in-testsuite?
OS: Mac OS X → All
Priority: -- → P3
Hardware: PC → All
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9 M10
Depends on: 406361
Crashtest checked in.
Flags: in-testsuite? → in-testsuite+
You need to log in before you can comment on or make changes to this bug.