-
Notifications
You must be signed in to change notification settings - Fork 284
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to investigate RSS memory leak? #4141
Comments
Take a look at v8-profiler, may be it can help |
Also, pls check response to #4148 |
This may also be helpfull - https://github.com/nodejs/node/blob/main/doc/contributing/investigating-native-memory-leaks.md |
There has been no activity on this issue for 11 months. The help repository works best when sustained engagement moves conversation forward. The issue will be closed in 1 month. If you are still experiencing this issue on the latest supported versions of Node.js, please leave a comment. |
it is worthwhile to see what is the system characteristics. summary of nodejs/node#31641 in this context is: rss stays high for ever, if there is no demand for memory in the system it is a known issue, and the current workaround is to ignore the observation, the growth will subside when there is a demand. or in other words - the system will adapt to the need, don't measure too much! :) |
It seems there has been no activity on this issue for a while, and it is being closed in 30 days. If you believe this issue should remain open, please leave a comment. |
It seems there has been no activity on this issue for a while, and it is being closed. If you believe this issue should remain open, please leave a comment. |
Details
I have a problem with one of my microservices that its RSS memory is rising and I don't know what should be a proper way of finding the real problem.
I already analyzed heapdumps and nothing can be found as I can see that heap is pretty stable.
process.memoryUsage()
is currently showing:It's a docker running inside of a k8s pod doing quite a lot of things.
amqplib
) processing lots of messagestypeorm
zlib.inflateSync
Heap:
RSS:
In the charts you can see that there are 2 instances of this microservice and both have exactly the same growth in RSS and exactly the same Heap.
Is there any way that I could analyse the other 1.3 GB of RSS memory which is not in the Heap ?
Node.js version
12.14.1
Example code
No response
Operating system
Alpine Linux v3.11 (in a Docker)
Scope
runtime
Module and version
Not applicable.
The text was updated successfully, but these errors were encountered: