Downgraded to scriptaculous 1.5.3 and prototype 1.4 and the leaks went away with the exact same code.  So, it’s definitely a Prototype problem.

 

Thomas, maybe you could talk to Sam about it.  I’ve emailed him in the past, but he never responds.  It probably has to do with the new Element.extend stuff (just a hunch since it was the most drastic change in the latest release).

 

Greg

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gregory Hill
Sent: Tuesday, May 09, 2006 8:46 AM
To: rails-spinoffs@lists.rubyonrails.org
Subject: [Rails-spinoffs] anyone used the new firefox leak monitor?

 

One of the Mozilla developer released a new extension to detect JS memory leaks:

 

https://addons.mozilla.org/firefox/2490/

 

If it’s accurate, it might be bad news for Prototype.  I have some code using prototype 1.4 with no leaks, but other code with 1.5 leaks on every single bindAsEventListener call, and a bunch of other places.  Not sure if it’s just me; I may just be using it incorrectly on the one project.  But, I can’t see anything at first glance to indicate that.

 

 Just downloaded the newer version of the plugin, so I’ll do some more digging. Anyone else used this yet?

 

Greg

_______________________________________________
Rails-spinoffs mailing list
Rails-spinoffs@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs

Reply via email to