5 ms·
> Does it provide any support for avoiding/detecting > Javascript "memory leaks" which are easy to create with > closures and anonymous functions? I don't
by joeyo 17y ago
> Does it provide any support for avoiding/detecting
> Javascript "memory leaks" which are easy to create with
> closures and anonymous functions?
I don't understand this. Do closures leak because of buggy javascript implementations or is there something about them that fundamentally prevents the interpreter from being able to tell when to garbage collect them?
- richcollins 17y agohttp://www.ibm.com/developerworks/web/library/wa-memleak/ http://www.ibm.com/developerworks/web/library/wa-memleak/
- andreyf 17y agoFirefox 3 no longer has this problem: https://developer.mozilla.org/en/interfacing_with_the_xpcom_cycle_collector https://developer.mozilla.org/en/interfacing_with_the_xpcom_... Reference counting GC is the problem, not closures.