Closed
Bug 343982
Opened 19 years ago
Closed 18 years ago
Leak DOM windows and document loading CNN
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
VERIFIED
FIXED
People
(Reporter: ajschult784, Unassigned)
References
()
Details
(Keywords: memory-leak, testcase)
Attachments
(1 file)
350 bytes,
text/html
|
Details |
If I load www.cnn.com with dbaron's leak logging, I leak 2 DOM windows and a document. The part that triggers the leak it is:
var s = new Object;
window.a = s;
s.d = document;
Reporter | ||
Comment 1•19 years ago
|
||
Leaked inner window 95b9d00 (outer 9668448) at address 95b9d00.
... with URI "file:///home/andrew/mozbugs/343982/test.html".
Leaked outer window 9668448 at address 9668448.
Leaked document at address 922d998.
... with URI "file:///home/andrew/mozbugs/343982/test.html".
Comment 2•19 years ago
|
||
I tracked down the regression range for this to between 2006-06-12 04:00 and 2006-06-13 04:00.
Checkins: http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=PhoenixTinderbox&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2006-06-12+03&maxdate=2006-06-13+05&cvsroot=%2Fcvsroot
The landing of the DOM agnostic branch and bug 176182 (still not sure what this was about) seem like likely candidates for regressions.
Severity: normal → major
Flags: blocking1.9a1?
Comment 3•18 years ago
|
||
dbaron's patch in bug 352911 fixes this.
Blocks: dom-agnostic
Depends on: 352911
Comment 4•18 years ago
|
||
Fixed by bug 352911. It would be great if you could verify this, Andrew.
Status: NEW → RESOLVED
Closed: 18 years ago
Flags: blocking1.9a1?
Resolution: --- → FIXED
Reporter | ||
Comment 5•18 years ago
|
||
no leak on the testcase or http://www.cnn.com/ with a current CVS build
Status: RESOLVED → VERIFIED
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
•