Re: IE6 memory leak - very fiddly
- From: Daniel Orner <dorner@xxxxxxxxxx>
- Date: Fri, 21 Nov 2008 09:58:15 -0500
Thomas 'PointedEars' Lahn wrote:
<snip>
Yes, it would. Prototype.js uses a lot of closures which create circular
references, many of them unnecessary, which are known to leak memory in IE
if host objects (here: DOM objects) are involved (because its GC can't
handle that), and it does not clean up after itself. Adding the `href'
attribute to the `a' element makes it a link in the first place, so that its
corresponding object shows up in the document.links NodeList, for example.
Read the FAQ Notes. <http://jibbering.com/faq/faq_notes/closures.html#clMem>
This sounds promising... however, it seems to work backwards from my understanding. I thought that the memory leak happens when a DOM node has a circular reference to a JavaScript object. You seem to be saying that when a link is created, it's added to document.links... wouldn't that then mean that the link would have *more* references than non-links and hence be *more* likely to leak, rather than stop leaking? Or is there something I'm not understanding properly?
Thanks for your help.
.
- Follow-Ups:
- Re: IE6 memory leak - very fiddly
- From: Thomas 'PointedEars' Lahn
- Re: IE6 memory leak - very fiddly
- References:
- IE6 memory leak - very fiddly
- From: Daniel Orner
- Re: IE6 memory leak - very fiddly
- From: Thomas 'PointedEars' Lahn
- Re: IE6 memory leak - very fiddly
- From: Daniel Orner
- Re: IE6 memory leak - very fiddly
- From: Thomas 'PointedEars' Lahn
- Re: IE6 memory leak - very fiddly
- From: Daniel Orner
- Re: IE6 memory leak - very fiddly
- From: Thomas 'PointedEars' Lahn
- IE6 memory leak - very fiddly
- Prev by Date: Re: IE6 memory leak - very fiddly
- Next by Date: Air Force1 and Air Jordan shoes PAYPAL wholesale
- Previous by thread: Re: IE6 memory leak - very fiddly
- Next by thread: Re: IE6 memory leak - very fiddly
- Index(es):
Relevant Pages
|