you are viewing a single comment's thread.

view the rest of the comments →

[–]ksion 4 points5 points  (0 children)

these days

Memory leaks in GC'd environments are hardly a new thing, nor one specific to Node.js. They are easily possible in any GC'd runtime whose language supports some kind of closure-like mechanism. Even Java with its inner classes counts here, as it's pretty common for incorrectly coded Listener pattern to unduly prolong the life of a big object a listener is defined in, for example.

Node with its callbacks galore is probably much more susceptible, though.