#28 ✓ resolved
John-David Dalton

IE Memory leak: Elements removed from dom are not having their observers stopped

Reported by John-David Dalton | April 18th, 2008 @ 04:48 PM | in 1.6.0.3

The fix recently applied:

http://github.com/sstephenson/pr...

Only solves part of the problem.

Elements that are removed from the document are not having their observers stopped.

We know things worked in 1.5.

We should probably implement a similar system.

Holding onto an element reference and removing its observers onunload.

http://dev.rubyonrails.org/attac... (patch may not be perfect but you get the idea)

Also we can "clean as we go" by having Element#update remove observers on the elements children (that are getting erased).

We can also add a second param to Element#remove and Element#replace that allows "house cleaning" as well.

This helps the memory usage on pages that don’t get refreshed often.

http://dev.rubyonrails.org/attac...

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

The Prototype JavaScript library.

Shared Ticket Bins

People watching this ticket

Pages