News for hackers. Stuff that matters.
Re:Google releases Closure, the tools behind the JS geniuses by joeyo on Monday November 09, 2009 @08:42PM (#932215)

  > 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?
Re:Google releases Closure, the tools behind the JS geniuses by richcollins on Monday November 09, 2009 @09:45PM (#932302)
Re:Google releases Closure, the tools behind the JS geniuses by andreyf on Monday November 09, 2009 @11:05PM (#932423)
Firefox 3 no longer has this problem: https://developer.mozilla.org/en/interfacing_with_the_xpcom_...

Reference counting GC is the problem, not closures.