Re: [jQuery] For Brandon Aaron
> Does someone know of a similiar ressource for Firefox, or is finding > memory leaks here more by chance? The article (not the msdn one) has a link to a Firefox extension called Leak Monitor: https://addons.mozilla.org/firefox/2490/. If that is what you mean by resource ... other than that I haven't seen an article like the msdn one for Firefox memory leaks. > Quite interesting might be the leak pattern page at msdn: > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ietechcol/dnwebgen/ie_leak_patterns.asp You know I've read that article so many times and sometimes I just don't get it but the more I read it, the more I start to get it. -- Brandon Aaron ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
Re: [jQuery] For Brandon Aaron
Hi Dan, It was titled as such because Brandon recently posted code to address a memory leak he found in JQuery's handling of events. I'll try to get a better title in place next time. Rey... > Also, why is this thread specifically for Brandon Aaron? I mean, this is a > mailing list, and you can email Brandon directly. If it's for everyone else, > then wouldn't 'Firefox still has multiple memory leaks, looky looky' be a > better title. ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
Re: [jQuery] For Brandon Aaron
It's not all as black and white as that article suggests. Whilst the user should be setting to null (or their JS framework library), it is ultimately the responsibility of the browser to prevent memory leaks from occuring. Some may point to Dojo and laugh at the memory leakage in their mail client, and they'd be right to. It is really quite bad that the library has so many loose ends, but again, Firefox should ultimately fix these issues. IE does this, and does it well, taking the necessity to explicity nullify out of the heads of developers. Why the Mozilla Foundation has waited so long to plug these particular leaks is unknown to me, but while these problems exists, the browser is still open to some big risks from JavaScript. By the way, if anyone (who does software dev) has actually looked at Firefox's JS code, they'll laugh. It's a real mess. Also, why is this thread specifically for Brandon Aaron? I mean, this is a mailing list, and you can email Brandon directly. If it's for everyone else, then wouldn't 'Firefox still has multiple memory leaks, looky looky' be a better title. Rey Bango-2 wrote: > > Hey Brandon, > > Looks like you hit it right on the head with your new event unloader: > > http://www.jackslocum.com/yui/2006/10/02/3-easy-steps-to-avoid-javascript-memory-leaks/ > > Check out point #2. > > Rey... > > ___ > jQuery mailing list > discuss@jquery.com > http://jquery.com/discuss/ > > -- View this message in context: http://www.nabble.com/For-Brandon-Aaron-tf2372925.html#a6617116 Sent from the JQuery mailing list archive at Nabble.com. ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
Re: [jQuery] For Brandon Aaron
Hi, > Quite interesting might be the leak pattern page at msdn: > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ietechcol/ >dnwebgen/ie_leak_patterns.asp > > Does someone know of a similiar ressource for Firefox, or is finding > memory leaks here more by chance? That link suggests (as you might have guessed before) that IE uses simple refference-counting for garbage collection. That is not a very good decission for a language like JavaScript where circular are not too exotic. I am not shure, but AFAIK the Mozilla-framework uses the sport model garbage collector, which doesn't have such a problem. If a Mozilla-browser leaks memory there are two possible reasons. One is that of course there can be bugs in the GC-implementation, and the other one can be memory-fragmentation. Christof ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
Re: [jQuery] For Brandon Aaron
Brandon Aaron schrieb: > Interesting ... it seems as though this would suggest that Firefox > leaks memory when event handlers aren't removed as well. I was under > the impression that only IE had this problem. I'm going to download > the leak tester and play around for myself and see what I find. Just wanted to mention that browsers, especially IE, do not leak by default. And to my understanding events also do not leak in any case. It depends on how these events are attached. Quite interesting might be the leak pattern page at msdn: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ietechcol/dnwebgen/ie_leak_patterns.asp Does someone know of a similiar ressource for Firefox, or is finding memory leaks here more by chance? -- Klaus ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
Re: [jQuery] For Brandon Aaron
I haven't checked the other libraries but jQuery does not leak in Firefox (according to the extension) on my leak test pages. -- Brandon Aaron On 10/2/06, Brandon Aaron <[EMAIL PROTECTED]> wrote: > Interesting ... it seems as though this would suggest that Firefox > leaks memory when event handlers aren't removed as well. I was under > the impression that only IE had this problem. I'm going to download > the leak tester and play around for myself and see what I find. > > -- > Brandon Aaron > > On 10/2/06, Rey Bango <[EMAIL PROTECTED]> wrote: > > Hey Brandon, > > > > Looks like you hit it right on the head with your new event unloader: > > > > http://www.jackslocum.com/yui/2006/10/02/3-easy-steps-to-avoid-javascript-memory-leaks/ > > > > Check out point #2. > > > > Rey... > > > > ___ > > jQuery mailing list > > discuss@jquery.com > > http://jquery.com/discuss/ > > > ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
Re: [jQuery] For Brandon Aaron
Interesting ... it seems as though this would suggest that Firefox leaks memory when event handlers aren't removed as well. I was under the impression that only IE had this problem. I'm going to download the leak tester and play around for myself and see what I find. -- Brandon Aaron On 10/2/06, Rey Bango <[EMAIL PROTECTED]> wrote: > Hey Brandon, > > Looks like you hit it right on the head with your new event unloader: > > http://www.jackslocum.com/yui/2006/10/02/3-easy-steps-to-avoid-javascript-memory-leaks/ > > Check out point #2. > > Rey... > > ___ > jQuery mailing list > discuss@jquery.com > http://jquery.com/discuss/ > ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
[jQuery] For Brandon Aaron
Hey Brandon, Looks like you hit it right on the head with your new event unloader: http://www.jackslocum.com/yui/2006/10/02/3-easy-steps-to-avoid-javascript-memory-leaks/ Check out point #2. Rey... ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
