Closed
Bug 764111
Opened 13 years ago
Closed 12 years ago
Leak nsDocument with <embed>, XML parsing error, carefully timed GC and CC
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jruderman, Assigned: mccr8)
Details
(Keywords: memory-leak, testcase, Whiteboard: [MemShrink:P2])
Attachments
(2 files)
1. Install https://www.squarefree.com/extensions/domFuzzLite3.xpi
2. Run a debug build with XPCOM_MEM_LEAK_LOG=2
3. Load the testcase.
4. Quit Firefox.
Result: trace-refcnt reports an nsDocument leak.
|
Reporter | |
Comment 1•13 years ago
|
||
1 nsDocument
0 nsGlobalWindow
0 nsDocShell
|
|
Reporter | |
Comment 2•13 years ago
|
||
Related to bug 689011?
|
Assignee | |
Updated•13 years ago
|
Whiteboard: [MemShrink]
|
|
Assignee | |
Updated•13 years ago
|
Assignee: nobody → continuation
|
||
Updated•13 years ago
|
Whiteboard: [MemShrink] → [MemShrink:P2]
|
|
Assignee | |
Comment 3•13 years ago
|
||
I followed the steps in comment 0, and no leak shows up.
I get this parsing error, though:
XML Parsing Error: no element found
Location: data:image/svg+xml,%3Cx%3E%3Cy%3E
Line Number 1, Column 7:<x><y>
------^
I changed <y> to </x> to fix the parsing error, and no leak there, either.
Can you reproduce this Jesse? Maybe there was some kind of parsing error related leak that was fixed in the meanwhile.
|
|
Reporter | |
Comment 4•12 years ago
|
||
WFM on mozilla-central
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
|
|
Assignee | |
Comment 5•12 years ago
|
||
Thanks. I tried changing the timeout value and that didn't seem to affect anything.
|
||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•