My question for the day is this:
I saw this comment:
'// break object reference to avoid memory leak
el = null;"
and I noticed you grabbed a new reference to header.element() for all the internal functions and discarded it when you finished by setting it to null.
I was wondering what's the memory leak you refer to?
Is it something to do with the nature of closures in JS i.e. a reference to private members still exists and is available to internal functions after the outer function is completed? Does this leak memory?
Back to your last question - closures do not leak memory by themselves but be very careful when you mix them with ActiveX objects.
(which also has a section about IE memory leak at the end :-)
This topic is archived.
Back to support forum
Version 2Looking for AW 2.6 ?
The old site is here.