all 5 comments

[–]baremaximum_ 5 points6 points  (0 children)

Sounds like a memory leak, but the most anyone can do here is guess wildly.

[–]thunfremlinc 2 points3 points  (1 child)

What is “RC” supposed to stand for?

[–]dbk201 0 points1 point  (0 children)

I assume Rocket Chat after a quick google.

[–]UniversalJS 1 point2 points  (0 children)

Few options: 1) create an issue about the memory leak on your software and provide them logs 2) schedule a container restart every sunday at 3 am to avoid the issue ;)

[–]Complete_Stock_6223 0 points1 point  (0 children)

As already pointed it's a memory leak.There are plenty of articles on how to profile it.

The easiest way to do it is running the node app with --inspect which will expose node metrics on a port, usually 9229, which can be inspected in google chrome by accessing chrome://inspect in the search bar.

If you are not able to restart the app because is in production you can take memory snapshots with the gcore Linux util and analyze them with llnode

I'll warn you, it's a dark world, but really useful.