ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frequent PM2 max_memory_restart triggers are often a threshold or cluster configuration issue rather than a leak. This guide shows how to recognize the pattern, run ordered checks, apply fixes tied to findings, and know when to escalate.
In deployments where pm2's max_memory_restart is used to guard against memory leaks, the threshold value is specified in megabytes but pm2's internal memory reporting may not align with the host operating system's RSS or container cgroup limits. This creates ambiguity about whether the restart trigger reflects actual process memory, aggregated container memo
PM2 provides the max_memory_restart option to automatically reboot a process when it exceeds a specific memory threshold. This is often used as a safeguard against gradual memory leaks in Node.js applications. In a production environment using PM2 v5.x, there is uncertainty regarding which specific memory metric the process manager monitors to trigger this r
nodejs