Closed Bug 253688 Opened 20 years ago Closed 17 years ago

memory leak in Mozilla when adding a eventListener from JavaScript and not removing it

Categories

(Core :: DOM: Events, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: feurle, Unassigned)

References

()

Details

(Keywords: memory-leak)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.7) Gecko/20040616
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.7) Gecko/20040616

When you add a eventListener to a DomNode and remember a object reference to the
DomNode the object is not removed when the Site is reloaded. See the URL with
the reproducer...

Reproducible: Always
Steps to Reproduce:
1. Open the URL
2. press on reload with enabled memory leak
3. reload once and see the process table/memory using

Actual Results:  
The Memory for bigObject is not freed after reload

Expected Results:  
bigObject should be freed after reload
Keywords: mlk
David, didn't you analyze a reference cycle along these lines recently?
Whiteboard: DUPEME
Product: Browser → Seamonkey
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Status: RESOLVED → UNCONFIRMED
No longer depends on: 241518
Resolution: EXPIRED → ---
Whiteboard: DUPEME
Assignee: general → events
Component: General → DOM: Events
Product: Mozilla Application Suite → Core
QA Contact: general → ian
I'm pretty sure I'm not seeing this anymore on the trunk after bug 241518 was fixed. A little hard to tell, you have to turn off bfcache to avoid seeing growth from that.

Do you agree?
Blocks: tibco
Works with:

Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago17 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.