-
Notifications
You must be signed in to change notification settings - Fork 30.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[3.2.0] Potential memory leak #2631
Comments
@Cinderella-Man Does this also happen with io.js 2.5.0? |
From what I'm seeing, the server process stabilizes at ~59-60MB rss, even if you keep restarting the client bash script. The stabilized memory amount can be improved a little bit (~2MB total on average) by draining the socket buffers sooner by adding Additionally, if you force the |
With io.js v2.5.0 I'm seeing roughly the same memory differences, except the rss has dropped uniformly for all scenarios by ~1MB. |
the new Buffer implementation makes rss much more unstable over longer runs now than it used to, thanks to something in |
My results for your script (given that by
Second client run on the same server:
You could see that both While @rvagg is correct here about the new Btw, speaking of 1.: if you replace a
|
Should we close this? |
Closing this for now. If someone can prove that there is a continual leak that never stops, then we can reopen this at that time. |
Recently I was stress testing my API and discovered that even very simple net server has a memory leaks. Is it possible that there's something wrong with it?
Server code:
Testing client bash script:
Starting iojs server(3.2.0):
After 10k calls server memory consumption increased from 21 to 45.5MB. Is that scripts' fault?
The text was updated successfully, but these errors were encountered: