News for hackers. Stuff that matters.
Re:Walmart Node.js Memory Leak by rcb on Saturday November 23, 2013 @04:41PM (#6787566)
This is impressive work by the Joyent team!

I've seen two sources of memory leaks in Erlang based systems: 1) unbounded process message queues, and 2) passing binaries across process (pid) boundaries.

Many beginning erlangers run into these, and they're relatively easy to identify and correct. With a little practice, these become easy patterns to recognize and avoid.

As far as httpc, I'm unaware of that bug -- but I can say that I recently worked on a commercial product that leveraged httpc as a core component of the service, and it worked fine.

Re:Walmart Node.js Memory Leak by andreypopp on Sunday November 24, 2013 @02:56AM (#6789049)
> As far as httpc, I'm unaware of that bug -- but I can say that I recently worked on a commercial product that leveraged httpc as a core component of the service, and it worked fine.

It was fixed soon after discovered.

Re:Walmart Node.js Memory Leak by ZephyrP on Sunday November 24, 2013 @12:46AM (#6788847)
Don't forget non tail-call methods and funky parse_transforms!