On Thu, Feb 3, 2011 at 11:26, roark <[email protected]> wrote: > setting FX object to null
I have only one second thought about that. As you specified a new anonymous function callback in addEvent, you also created it in the memory (+ a pointer from the object's event handler to the function). Maybe you should also save and later destroy the reference to the custom event callback, because that part of the cleanup may not be automatic. If I recall correctly this (custom event + destroying parent) is the exact way to create some old memory leak, but I am not sure if it is still in the wild or did it apply only to IE6. p.s.: you should care about meory leaks only if you use them in a loop of 100,000 items or similar, if you have less than few 100 items you'll never notice anything and really couldn't care less. I wouldn't. :)
