Yeah, there is already discussion about that particular article (which isn't strictly accurate).
http://www.nabble.com/Fixing-jQuery%27s-Memory-Leak-tf2358975.html Rich Manalang wrote: > > I was just reading Jack Slocum's article on easy ways to avoid > javascript leaks > (http://www.jackslocum.com/yui/2006/10/02/3-easy-steps-to-avoid-javascript-memory-leaks/). > He mentions a FF plugin called the Leak Monitor > (http://dbaron.org/mozilla/leak-monitor/). I just tried this on one > of my web apps that use jQuery... and sure enough, I found some > leaks... > > Leaks in window 0x4c333a8: > [+] [leaked object] (49afa20, > http://myhostname/monkeygrease/lib/jquery/jquery.js, 1186-1203) = > function () { > if (!jQuery.isReady) { > jQuery.isReady = true; > if (jQuery.readyList) { > for (var i = 0; i < jQuery.readyList.length; i++) { > jQuery.readyList[i].apply(document); > } > jQuery.readyList = null; > } > if (jQuery.browser.mozilla || jQuery.browser.opera) { > document.removeEventListener("DOMContentLoaded", > jQuery.ready, false); > } > } > } > [ ] guid = 1 > [ ] prototype (1f7b208) = [object Object] > > I need to track down the cause, but just wondering if anyone's had > leak problems with jQuery? > > Rich > > _______________________________________________ > jQuery mailing list > discuss@jquery.com > http://jquery.com/discuss/ > > -- View this message in context: http://www.nabble.com/jQuery-leaks...-tf2434894.html#a6792932 Sent from the JQuery mailing list archive at Nabble.com. _______________________________________________ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
