-
Notifications
You must be signed in to change notification settings - Fork 267
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
element-desktop crash after ~15 seconds after start (killed by OOM-killer #1564
Comments
Fixed after update element-desktop-night to Element Nightly: 2024030901 |
Reproduce in last element-desktop 1.11.60 in such enveronment.
|
Recheck on element-desktop version 1.11.65 (debian 12 official element.io repo):
In result - I see white empty screen of element-desktop. |
I am experiencing this same issue. I am using version 1.11.65 (ubuntu 22.04) `/home/chris/.config/Element exists: yes <--- Last few GCs ---> [1:0x22bc078e0000] 1637 ms: Mark-Compact (reduce) 342.0 (364.9) -> 213.6 (219.4) MB, pooled: 0 MB, 113.97 / 0.00 ms (+ 0.0 ms in 0 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 114 ms) (average mu = 0.930, current[1:0x22bc078e0000] 1995 ms: Mark-Compact (reduce) 213.6 (219.4) -> 213.6 (218.4) MB, pooled: 0 MB, 357.31 / 0.00 ms (average mu = 0.764, current mu = 0.000) last resort; GC in old space requested <--- JS stacktrace ---> [24397:0502/132310.442320:ERROR:v8_initializer.cc(799)] V8 javascript OOM (CALL_AND_RETRY_LAST). The problem is isolated to a single conversation, all others work fine. The other users had sent me 2 short voice messages which is pretty normal behavior and doesnt cause problems, but today I am unable to view this conversation anymore through element-desktop but works fine from the android element app. I deleted those 2 voice messages from my phone that preceeded the crashing in hopes that it would clear the problem but it had no effect, the conversation with that user seems to be permanently polluted by something blowing out the javascript memory limit. The effected conversation will render fine for about 5-10 seconds after I open it and then the oom error gets generated and the whole element client turns white and I have to force close it and start back up and quickly change to another conversation to keep it from crashing again. I monitored memory usage and while viewing any other conversation the memory usage for element stays at about 250mb of resident memory, soon as I click on the effected conversation it immediately and rapidly starts ballooning out until it hits about 5gb of resident memory and then crashes. I dont think its relevant as this seems to be a memory limit defined in javascript, but this system has 128gb of memory so it is not a memory shortage issue. |
Update on this problem. This is an intermittent issue that seems to go away on its own but does return. It stopped crashing when opening the message window with that user even with additional voice messages since I added my last comment, but the problem is back now with the same user and voice messages again. I tried using the web version at app.element.io but it also crashes the same way when opening the chat with that user. I have not been able to coorelate the length of messages at all as it seems to be random on what messages cause this behavior |
Steps to reproduce
Where are you starting? What can you see?
Debian 12 amd64, wayland
I use my server rsprim.ru (debian 11 version:
matrix-synapse-py3 1.89.0+bullseye1
)What do you click?
Crash aelement-desktop and element-desktop-nightly:
All above versions was crashed at simply start.
But I try clear data-dir, but this was not help:
rm -rf ~/.config/Element-Nightly
top
show that element-desktop eat RAM up to 5,3 Gb)dmesg show:
in console:
Outcome
What did you expect?
What happened instead?
Operating system
debian 12
Application version
element-nightly 2024030801
How did you install the app?
official element.io repo for debian 12
Homeserver
matrix-synapse-py3 1.89.0+bullseye1
Will you send logs?
No
The text was updated successfully, but these errors were encountered: