News for hackers. Stuff that matters.
Re:Walmart Node.js Memory Leak by andreypopp on Saturday November 23, 2013 @01:26PM (#6786860)
2 or 3 years ago I hit memory leak in Erlang's stdlib's httpc... just saying.
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!
Re:Walmart Node.js Memory Leak by lpgauth on Sunday November 24, 2013 @12:28PM (#6790227)
I wouldn't recommend httpc to anyone... It's really slow and doesn't scale at all. There's plenty of better alternatives: lhttpc, ibrowse, hackney.
Re:Walmart Node.js Memory Leak by gcb1 on Saturday November 23, 2013 @03:17PM (#6787277)
is inet part of stdlib?
Re:Walmart Node.js Memory Leak by andreypopp on Saturday November 23, 2013 @03:59PM (#6787405)
Well, it's a part of OTP, which is, I believe, "the true" stdlib of Erlang.