Memory leak or garbage collection? #18948
Replies: 1 comment 1 reply
-
|
Hi @deribaucourt, It doesn't look like a memory leak. Observe for a few days/week and check the memory usage again. Post a screenshot if it keeps growing. |
Beta Was this translation helpful? Give feedback.
-
|
It is most likely a memory leak. Regardless of the version, netdata tries to occupy all available memory for the container. Then the container restarts. I started from 100mb limit, now I see the very same thing for 400mb. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
Our system is going to run netdata without interruption and the memory consumption of the netdata process looks like a memory leak.
However, by looking at the live demo's profile, we can see a similar growth pattern which looks logarithmic, but then it cycles down when it reaches about 100MiB. https://app.netdata.cloud/spaces/netdata-demo/rooms/apache/overview
We must avoid a memory leak on our system so we would like to understand this mechanism and make sure the garbage is going to be collected regularly. Can you indicate what part of the code would produce this memory behavior and how could we change the freeing trigger to run it more regularly on our system?
Thank you for your time :)
Beta Was this translation helpful? Give feedback.
All reactions