Memory leak on Render.com server

[andychongyz]

Hi, I deployed a Remix app on Render.com as a node app, not serverless. The memory usage increases over time, and it seems like a memory leak. Is this normal, and if not, how can I identify the part of the code causing it? I'm new to tracing memory leaks with node.js apps. Thank you!

[chigia001]

Do anything happen at that CPU spike? That CPU spike also happen when your memory reduce, so my guess is nodes start their Major GC and your memory return to normal afterward. This is normal for Nodejs, but Nodejs GC can also block main thread so server might become unreponsive during that time.

[andychongyz]

Some updates, I periodically restart the app for now using a CRON task. I found an article from Kent on how to identify the memory leak, but I haven't had the time to work on it yet.

[geiszla]

Any updates on this or tips on how to handle it? We are also experiencing this issue, and when the garbage collection happens the requests to the server time out and return 500 errors.

I've checked the memory dump in Google Cloud, but I couldn't find anything that would take up considerable share of the heap space.

Here's a flame graph of the heap dump.