0.6.18 Huge Memory Leaks

[pyrostrex]

Today, I was excited to test the new 0.6.18. But, then, suddenly in just 10 minutes after restarting my server, my 2gb memory usage raised up to 40% but when i switched back to 0.6.17, my memory usage is still maintain below 10%. It is disaster in 20 minutes which raised my memory to 70%++. At first I thought it was my server's messy coding but then, I changed to 0.6.17, it went back to normal.

[rauchg]

Are you sure it was socket.io ? We didn't change much in the server for this release, it was mostly client.

[pyrostrex]

Hmm, after some more investigation, I also got this with 0.6.17, this was first detected after I updated my npm. Sigh, will investigate more. But I'm sure it is not my server problem and the only dependencies I used was socket.io and express. nothing else.

[pyrostrex]

I think I'm positive that this is socket.io's memory leak. I've even changed my base64 encoder from brainfucker's encoder to nodejs encoder and my other server that was currently 100% using expressjs doesnt have any memory leak problem. So, the only thing left is socket.io. Maybe somewhere there is a broken connection reference that wasn't fully removed. But I will keep in investigating about this problem. The weird thing is it only happens after some time.

[pyrostrex]

Right now, I think I'm back to negative about socket.io having memory leak. Sigh, I still can't find the answer. Still debugging my server. Thank you. I think I'm gonna close this as it is not correct.