JAP_WS_LOCAL.js seems memory leak? Worse then JAP_WS_LOCAL.py

[GoogleCodeExporter]

What steps will reproduce the problem?
1.remote:JAP_WS_REMOTE_NODE_OPENSHIFT-2.0.0-SNAPSHOT
2.local:JAP_WS_LOCAL_NODE-2.0.0-SNAPSHOT
3.run:node JAP_WS_LOCAL.js

What is the expected output? What do you see instead?
At firest,the process takes up 9M memory.After surfriding
 and watching Youtube for about 3 hours,it eats 210M.

What version of the product are you using? On what operating system?
os: Archlinux + Xfce4.10 + Chromium
$ node --version
v0.8.21

Please provide any additional information below.
Maybe memory leak,or bad garbage collection.Worse then JAP_WS_LOCAL.py

Original issue reported on code.google.com by westmin...@gmail.com on 28 Feb 2013 at 12:50

[GoogleCodeExporter]

Can you test attached JAP_WS_LOCAL.js and TUNNEL.js (copy to 
JAP_WS_LOCAL_NODE-2.0.0-SNAPSHOT\JAP)?

Thanks :)

Original comment by jeroen.v...@gmail.com on 28 Feb 2013 at 7:40

Attachments:

• JAP_WS_LOCAL.js
• TUNNEL.js

[GoogleCodeExporter]

Still the same.
I play a youtube playlist with 100+ hours videos for 4 hours consecutively, 
finally the process takes up 200M+ memory.

Original comment by westmin...@gmail.com on 28 Feb 2013 at 8:14

[GoogleCodeExporter]

I commented out all the log codes e.g.
//console.log("server.connect");
When watching youtube videos,I can see the process release memory regularly.
However,it still takes up memory slowly to 200M+.

Original comment by westmin...@gmail.com on 28 Feb 2013 at 8:54

[GoogleCodeExporter]

Maybe a problem with OPENSSL? https://github.com/joyent/node/issues/2653

Original comment by jeroen.v...@gmail.com on 28 Feb 2013 at 9:28

[GoogleCodeExporter]

Or maybe a problem with NODE? Maybe test with (unstable) NODE 0.9.x?

Original comment by jeroen.v...@gmail.com on 28 Feb 2013 at 9:53