Memory leak in linux with high concurrency
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
The same happened to me also, pm2 is leaking memory it keeps the data in memory. I have removed pm2 now everything is working fine.
Ram usage is constantly increasing.
Originally posted by @rachitbucha in https://github.com/Unitech/pm2/issues/5052#issuecomment-1769832014
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported memory growth in PM2 under high concurrency and compare RAM usage with PM2 removed, as described in the issue. The payload names no files or tests, so use the reproduction to locate the relevant process-management entry point. Done means identifying and fixing the leak and confirming memory remains stable during sustained concurrency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100