Open
Bug 700768
Opened 13 years ago
Updated 2 years ago
Leak nsDocument with CSS filter, view-source
Categories
(Core :: CSS Parsing and Computation, defect)
Tracking
()
NEW
People
(Reporter: jruderman, Unassigned)
References
Details
(Keywords: memory-leak, testcase)
Attachments
(2 files)
1. Run a debug build of Firefox with XPCOM_MEM_LEAK_LOG=2
2. Load the testcase
3. Quit Firefox
Result: trace-refcnt reports 1 nsDocument leaked
|
Reporter | |
Comment 1•13 years ago
|
||
|
||
Comment 2•12 years ago
|
||
Still leaks.
|
|
||
Comment 3•12 years ago
|
||
In the shutdown CC, the nsDocument has two references, one from nsNodeInfoManager, one unknown, the latter which is keeping this alive. I'm not brave enough to attempt refcount logging nsDocument. bug 704240 might provide more information.
|
|
||
Updated•9 years ago
|
Assignee: hsivonen → nobody
|
|
||
Comment 4•9 years ago
|
||
I'm trying out the DMD heap scanner on this. It looks like maaaaaybe sCachedMainThreadChain has a reference to the document, which would be a strong one. I'm not sure if that makes any sense, though, and I have a bunch more references to dig through.
|
||
Comment 5•9 years ago
|
||
sCachedMainThreadChain should never have pointers to anything. It just caches the storage for the event target chain (if the previous chain was <= 128 event targets)
|
|
||
Comment 6•9 years ago
|
||
I think bug 1172165 will "fix" this by making the link not work.
Depends on: 1172165
|
|
||
Comment 7•9 years ago
|
||
Well, maybe not, but it is worth trying it after that lands.
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•