Hi all We faced the memory leak probleam when we migrate our socket.io from http to https. The memory slowly growing up and at some point, CPU suddenly goes to 99% without responsive and finally coredumped by abort().
I tried to shutdown all the connections by using iptables, and find that the js heap memory did going down, but the whole process memory(get from ps aux) seems not decreased a lot. Here is the memroy situation after i shutdown 10000 TCP ESTABLISHED connections: ------------------------------ process memory consume: miles 31370 15.3 0.7 973188 *371732* pts/7 Sl 22:35 7:08 ./bin/node --trace-gc --trace-gc-verbose --expose_gc server.js js gc log: [31370] 2875093 ms: Mark-sweep 9.3 (54.0) -> 9.3 (54.0) MB, 11 ms [gc extension] [GC in old space requested]. ---------------------------- 1. This maybe because the process does not give memory back to OS for some kind of user space memroy alloc policy or there's hole in the page 2. It's a normal memory leak from process heap(allloced by new/malloc) Does someone have good ideas to handle this situation? Thanks. -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/677421b0-220c-4062-99c4-b78e01e05b43%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
