Re: socket.io over https memory leak issue

Our team is now facing this problem, that a big memory leak, when sixteen users visit our website, the memory was rose 350 MB ：(

and the version of the socket.io that we use is 0.9, which version you are using.

0.9.14, Same version as yours. Memory can easily bolw up to 1.8G under 10000 connections.

i know, it might be not what you want to hear, but socket.io has had a 1.0 release, which was a bigger step and should have solved many problems ppl had with 0.9 version, so may be you want to update? i'm not sure about if the maintainer want to support the know as buggy version, you should update anyway soon.

My app is seeing the same problem, memory blowing up after some time and then CPU going to 100%. We've been using socket 1.x since mid August, so that doesn't solve it. Does anyone have any ideas as to what to try next?

For us, a partial fix was to make sure that we only use websockets as a transport mechanism. We are still leaking memory, but much less so than before. If websockets suit your app, the line you need to configure them is this:

io.connect(serverUrl, { transports: ['websocket'] })

I'd like to make sure I get rid of the leak completely though. Any help would be appreciated.

My app is seeing the same problem, memory blowing up after some time and then CPU going to 100%. We've been using socket 1.x since mid August, so that doesn't solve it. Does anyone have any ideas as to what to try next?

You might want to take a look at https://github.com/Automattic/engine.io/commit/5255647e994ec0a0a0f76100c1544ac2f7c8592d which got released in socket.io 1.21: https://github.com/Automattic/socket.io/commit/24d06d76ddf0808ac370e39fd57329d3048d73e4.

Oh sweet! I'll test that and report back.

My app is still leaking. However, it's unclear if the leak originally was due to socket.io or not.