Bug Tracker

Modify

Ticket #3553 (closed enhancement)

Opened 5 years ago

Last modified 11 months ago

use of removeChild in IE leaking memory

Reported by: crobinson Owned by: flesler
Priority: minor Milestone: 1.4
Component: core Version: 1.2.6
Keywords: removeChild memory leak Cc: crobinson
Blocking: Blocked by:

Description

attached is a zip file with a small test you can run after patching and 2 screen shots, on of the sIEve results of reqular jQuery vs a modified version I made to test the theory. In the screen shots you can see that the memory reclaimed in the Delta's its on average higher in the modified version.

Take note that the tests will run 250 iterations before it will stop.

This is only an issue in IE.

for a write up in more detail visit:  http://www.outsidethediv.com/2008/10/removechild-vs-the-garbage-bin/

Attachments

memory-test.zip Download (106.0 KB) - added by crobinson 5 years ago.
memory-usage-modified-jquery.zip Download (218.6 KB) - added by crobinson 5 years ago.
memory-usage-regular-jquery.zip Download (220.5 KB) - added by crobinson 5 years ago.

Change History

Changed 5 years ago by crobinson

Changed 5 years ago by crobinson

Changed 5 years ago by crobinson

comment:1 Changed 5 years ago by flesler

  • need changed from Review to Test Case
  • Owner set to flesler
  • Status changed from new to assigned

Ok, haven't used sIEve more than once... shouldn't the #leaks column have a number that is diff than 0 if it'd have leaks ? I see that the regular takes less time.

Also... while doing some googling on the issue, I found this:

 http://trac.dojotoolkit.org/ticket/1727#comment:15

Can you try that with your demo and see if it solves the so called leak ?

comment:2 Changed 5 years ago by flesler

  • Cc crobinson added

comment:3 Changed 4 years ago by yehuda

  • Milestone changed from 1.3 to 1.3.3

comment:4 Changed 3 years ago by snover

  • Status changed from assigned to pending

This ticket has been marked as missing a test case. In an effort to reduce the number of outstanding tickets in the bug tracker, it will be closed automatically in 30 days. In order to prevent this from happening, please provide a working test case. If a test case has already been provided and our records are wrong, please respond to the ticket so that it can be fixed. Thank you!

comment:5 follow-up: ↓ 6 Changed 3 years ago by trac-o-bot

  • Status changed from pending to closed

Automatically closed due to 14 days of inactivity.

comment:6 in reply to: ↑ 5 Changed 11 months ago by anonymous

Replying to trac-o-bot:

Automatically closed due to 14 days of inactivity.

There is a test case attached to this. This should be reopened

Please follow the  bug reporting guidlines and use  jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.

View

Add a comment

Modify Ticket

Action
as closed
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.