-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Massive memory leak, very low volume room #25120
Comments
I noticed something very odd, perhaps this is related. Looking at Screen cap from top I can't get the table to format, but take a look at the bold text 1Tb!!
|
This issue seems to be tracked here: element-hq/element-desktop#680 |
In my case the PC never sleeps. So I am not sure it's the same issue. |
Not sure if related or not. I can report I've been running the heap monitor for three days and there is little or no increase. It's been sitting at ~50-60MB the whole time. That does not match top, which reports more like 1.2GB, so not sure if the two are at all related. What I did do at last restart is close some old unverified sessions. Could that be an area where such a memory leak occurs? 58941 user 2525284 89944 0.0 1.2 0:03.38 /usr/lib/firefox-esr/fi+ 28 0 500 142052 144684 0 670 144684 30670 user 1131.9g 33544 0.0 1.2 5:42.57 /opt/Element/element-de+ 17 25816 123256 371612 139928 5 870 165744 55939 user 2564996 83836 0.0 1.2 0:17.20 /usr/lib/firefox-esr/fi+ 28 0 500 148412 137908 0 670 137908 |
Steps to reproduce
Element desktop on VM
Outcome
What did you expect?
Should just work as it does on a windows PC
What happened instead?
After 3-4 days 12G memory used. Eventually crashes PC due to available VM memory being used up.
Done a restart and discovered developer mode, which has a JS heap monitor, will run that for a few days.
Operating system
Debian 11
Application version
Element version: 1.11.26 Olm version: 3.2.12
How did you install the app?
Don't recall - ages ago.
Homeserver
Private Synapse
Will you send logs?
No
The text was updated successfully, but these errors were encountered: