Adrian: what I was trying to say is that I *used* to cover memory leaks
(in the 5th edition) but I've taken that stuff out in the 6th edition
because I believe that it is no longer really a problem (except in IE6).
If I'm mistaken there is still time for readers of this list to correct
me and get the discussion of cyclic memory leaks re-inserted.
David
On 12/07/2010 07:54 AM, Adrian Olaru wrote:
@David, it will be nice to see a chapter about memory leaks in browser
in your 6th version of the book.
On Tue, Dec 7, 2010 at 5:49 PM, David Flanagan <[email protected]
<mailto:[email protected]>> wrote:
On 12/07/2010 04:18 AM, Christophe Porteneuve wrote:
Hey there,
The core source of memory leaks in JS is circular references
between the
DOM and the JS object space. Essentially this happens when you
maintain
refs to DOM nodes from your JS *and* put refs to JS objects from the
same closure in expando properties of these DOM nodes.
My understand is that this pattern of leaks was always IE-specific
and has been (at least mostly) fixed in IE7. (But I have not done
any primary research into the issue myself.)
I have removed my discussion of cyclic memory leaks from the (not
yet out) 6th edition of my JavaScript book.
David Flanagan
_______________________________________________
JSMentors mailing list
[email protected] <mailto:[email protected]>
http://jsmentors.com/mailman/listinfo/jsmentors_jsmentors.com
_______________________________________________
JSMentors mailing list
[email protected]
http://jsmentors.com/mailman/listinfo/jsmentors_jsmentors.com
_______________________________________________
JSMentors mailing list
[email protected]
http://jsmentors.com/mailman/listinfo/jsmentors_jsmentors.com
