RocketChat / RocketChat/Rocket.Chat
The entire rocketchat web UI would crash if there is too many livechat (that wasnt closed)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
The entire rocketchat web UI would crash if there is too many livechat (that wasnt closed)
Steps to reproduce:
Having more than thousands livechats that was never closed or purged... It seems like when web UI loads, it would try to load up all of the historical livechats (which includes all of the ones that wasn't closed). Causing huge lag spike and crash. Making web UI impossible to use. Especially when livechat is basically used by visitors on use and dump basis.
Expected behavior:
At least lazy load the first 50.. but not all of the chats.
Actual behavior:
Loading all thousands of chats at once on web UI logging in, causing crash.
Server Setup Information:
- Version of Rocket.Chat Server: latest version - still happens.
- Operating System: docker on linus.
- Deployment Method: docker
- Number of Running Instances: 1
- DB Replicaset Oplog: na
- NodeJS Version: na
- MongoDB Version: na
Client Setup Information
- Desktop App or Browser Version: All tested browser. Chrome, firefox, IE. All crash. All crash on all devices.
- Operating System: All OS. Windows, iOS, android, etc.
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 named. Reproduce the crash by loading the web UI with thousands of unclosed livechats, then trace the livechat history loading path. Done means the UI loads an initial limited set, such as 50 chats, without loading every historical chat or crashing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100