Closed
Bug 353842
Opened 18 years ago
Closed 18 years ago
Login to Litmus leaks
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 353090
People
(Reporter: JasnaPaka, Unassigned)
References
()
Details
(Keywords: memory-leak)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20060922 BonEcho/2.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20060922 BonEcho/2.0
I used leak-gauge.pl (http://dbaron.org/log/2006-01#e20060110a) and
Firefox 2.0 NB, clean profile. No problem with Firefox Trunk.
Reproducible: Always
Steps to Reproduce:
1. Visit Litmus (http://litmus.mozilla.org/).
2. Login to Litmus.
3. Close Firefox.
Actual Results:
Leaked inner window 28e0358 (outer 203c1a8) at address 28e0358.
... with URI "http://litmus.mozilla.org/index.cgi".
Leaked inner window 242af58 (outer 203c1a8) at address 242af58.
... with URI "http://litmus.mozilla.org/login.cgi".
Leaked outer window 203c1a8 at address 203c1a8.
Leaked document at address 23d5260.
... with URI "http://litmus.mozilla.org/login.cgi".
Summary:
Leaked 3 out of 14 DOM Windows
Leaked 1 out of 45 documents
Leaked 0 out of 5 docshells
Reporter | ||
Updated•18 years ago
|
Version: unspecified → 2.0 Branch
Comment 1•18 years ago
|
||
Fixed on trunk between 2006-09-19-04 and 2006-09-20-04. So, this is a dupe of bug 353090.
A blog/newsgroup post should probably be made about this, but dbaron has recently landed some patches on trunk that fix /lots/ of leaks, so if you're doing leak testing in the next few weeks, it would be good to test and see if we leak on trunk before you file bugs.
Assignee: nobody → general
Component: General → DOM
OS: Windows XP → All
Product: Firefox → Core
QA Contact: general → ian
Hardware: PC → All
Version: 2.0 Branch → 1.8 Branch
Comment 2•18 years ago
|
||
*** This bug has been marked as a duplicate of 353090 ***
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
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
•