Comments on: jQuery Leaking Memory:-Be careful while using in big applications

By: Stream Direct

Stream Direct — Sat, 27 Nov 2010 05:59:39 +0000

I would like to thank you for the efforts you have made in writing this article. I am wish the same best work from you in the future as well kind regards.

By: Anonymous

Anonymous — Mon, 23 Nov 2009 01:07:38 +0000

Check out this article
http://www.codeproject.com/KB/ajax/jqmemleak.aspx

By: Hozi

Hozi — Thu, 30 Jul 2009 15:10:19 +0000

Great article that aggregates fixes to all the various jQuery memory leaks due to UpdatePanel refreshes at https://www.quattrosource.com/2009/07/fixing-jquery-memory-leaks-in-asp-net/

By: Brandon Aaron

Brandon Aaron — Tue, 21 Apr 2009 20:35:00 +0000

Just simply needed to null out the orphaned div element. Added the following line to jQuery.support:

// release memory in IE
div = null;

By: admin

admin — Tue, 21 Apr 2009 19:07:00 +0000

@Bradon
Great!
Could you please elaborate more on the fix or provide the readers with some link to your blogpost as what exactly you changed.

Thanks anyways

By: Brandon Aaron

Brandon Aaron — Tue, 21 Apr 2009 19:02:00 +0000

I just checked in a fix for the memory leaks created at runtime by jQuery. Meaning you won’t have to comment out that code. 🙂

By: Anonymous

Anonymous — Tue, 21 Apr 2009 11:05:00 +0000

More like Internet Explorer leaks memory through crappy implementation.

By: Danny Tuppeny

Danny Tuppeny — Mon, 20 Apr 2009 10:38:00 +0000

There’s a discussion on the jQuery dev list:

http://groups.google.com/group/jquery-dev/browse_thread/thread/d127129441e26e52

I don’t think commenting out the code you posted is a good idea – I believe John Resig mention it only to identifier if that’s where the leaks come from. I beleive without the code jQuery if you clone things in IE you and alter the vent handlers, it may affect the source nodes.