Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Large rooms will eat RAM until killed by the OS
See original GitHub issueEg.
Steps? Join xmpp:#matrix#matrix.org@bridge.xmpp.matrix.org?join ~5k users
FYI, Conversations (at least 2.4.0 or later) and apparently Yaxim handle these ok.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Unable to join some large rooms due to high RAM consumption
Joining some large rooms, such as #freenode_#haskel:matrix.org (1.4k members), fails because synapse eats up all the available memory ...
Read more >Memory Management
If there is no swap space left on the disk and there is no large enough hole, the process will have to be...
Read more >Why does my Java process consume more memory than Xmx?
Did you know that 20% of Java applications have memory leaks? Don't kill your application – instead find and fix leaks with Plumbr...
Read more >Operating Systems: Main Memory
Every instruction has to be fetched from memory before it can be executed, and most instructions involve retrieving data from memory or storing...
Read more >prevent system freeze/unresponsiveness due to swapping run ...
4) keep important programs (X11, bash, kill, top, ...) in memory and never swap those => can this be done? how? perhaps only...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Looks like on HEAD it’s not leaking any more (at least with the current ~2.2k users), it did jump to 1.5Gb RAM for Firefox, but after the roster was loaded is backed down to 500Mb.
Good job @jcbrand
Thanks, I’m closing this then.