You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Where are you starting? What can you see?
I open a chat with several audio messages from a bridged WhatsApp group.
What do you click?
I type a message or stay in the chat message.
Outcome
What did you expect?
Normal behavior, no slowdowns or crashes
What happened instead?
Typing is very sluggish; sometimes, it goes to a white page just by keeping the chat open. It looks related to downloading/loading the voice messages. If I wait long enough, it stabilizes. But if I switch back to another conversation and then back to it, the problem persists.
Running from the command line, I see this in the logs:
<--- Last few GCs --->
[1686:0x7fc719962000] 7869 ms: Scavenge 149.2 (161.0) -> 148.5 (168.3) MB, 43.35 / 0.00 ms (average mu = 1.000, current mu = 1.000) allocation failure;
<--- JS stacktrace --->
[1686:1008/194324.308983:ERROR:v8_initializer.cc(771)] V8 javascript OOM (Scavenger: semi-space copy).
I can't run /rageshake since Element is crashing, but let me know if there's more needed to investigate the issue.
Operating system
macOS 13.4.1 x64, running inside a QEMU VM (but reproducible on M1 Macs, too)
Application version
Element 1.11.45
How did you install the app?
brew install Element, but has since been updated by Element's updater
Homeserver
Synapse 1.93.0
Will you send logs?
Yes
The text was updated successfully, but these errors were encountered:
Steps to reproduce
Where are you starting? What can you see?
I open a chat with several audio messages from a bridged WhatsApp group.
What do you click?
I type a message or stay in the chat message.
Outcome
What did you expect?
Normal behavior, no slowdowns or crashes
What happened instead?
Typing is very sluggish; sometimes, it goes to a white page just by keeping the chat open. It looks related to downloading/loading the voice messages. If I wait long enough, it stabilizes. But if I switch back to another conversation and then back to it, the problem persists.
Running from the command line, I see this in the logs:
I can't run /rageshake since Element is crashing, but let me know if there's more needed to investigate the issue.
Operating system
macOS 13.4.1 x64, running inside a QEMU VM (but reproducible on M1 Macs, too)
Application version
Element 1.11.45
How did you install the app?
brew install Element, but has since been updated by Element's updater
Homeserver
Synapse 1.93.0
Will you send logs?
Yes
The text was updated successfully, but these errors were encountered: