Leak nsDocument with <embed>, XML parsing error, carefully timed GC and CC

RESOLVED WORKSFORME

Status

()

RESOLVED WORKSFORME
7 years ago
6 years ago

People

(Reporter: jruderman, Assigned: mccr8)

Tracking

(Blocks: 1 bug, {memory-leak, testcase})

Trunk
x86_64
Mac OS X
memory-leak, testcase
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [MemShrink:P2])

Attachments

(2 attachments)

(Reporter)

Description

7 years ago
Created attachment 632363 [details]
testcase

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

7 years ago
Created attachment 632364 [details]
Leak log

1 nsDocument
0 nsGlobalWindow
0 nsDocShell
(Reporter)

Comment 2

7 years ago
Related to bug 689011?
Whiteboard: [MemShrink]
Assignee: nobody → continuation
Whiteboard: [MemShrink] → [MemShrink:P2]
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

6 years ago
WFM on mozilla-central
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WORKSFORME
Thanks.  I tried changing the timeout value and that didn't seem to affect anything.
You need to log in before you can comment on or make changes to this bug.