> Does it provide any support for avoiding/detecting > Javascript "memor... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		joeyo on Nov 10, 2009 \| parent \| context \| favorite \| on: Google releases Closure, the tools behind the JS g... `> 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 on Nov 10, 2009 [–]

http://www.ibm.com/developerworks/web/library/wa-memleak/

andreyf on Nov 10, 2009 | [–]

Firefox 3 no longer has this problem: https://developer.mozilla.org/en/interfacing_with_the_xpcom_...

Reference counting GC is the problem, not closures.

Consider applying for YC's Summer 2026 batch! Applications are open till May 4
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact