RocketChat / RocketChat/Rocket.Chat
Rapid Increase in Memory Consumption (400MB in one momemnt)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
Might be related to #25199 and other topics.
In a freshly restarted production machine, I see memory hopping up by over 400MB at times (2x - 3x per day), meaning that the server needs to be restarted every other day.
Node seems to consume most of this memory.
Steps to reproduce:
Run a fairly standard RocketChat setup with Docker – MongoDB one the same server. Using GridFS for static files (migrating soon)
Expected behavior:
Memory usage stays consistent or grows with usage.
Actual behavior:
Random jumps in memory usage that sustain and never go down again
Server Setup Information
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
No source files, tests, or entry points are identified. Start by reproducing the issue with the documented Rocket.Chat Docker setup, including MongoDB and GridFS, then inspect sustained Node memory growth; done means identifying the cause of the jumps and verifying that memory remains stable under comparable usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, mongodb, node.js, typescript
- Domain
- backend, databases, infrastructure, performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100