Skip to content

Full Freeze in one specific channel #27012

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.

Sign up for GitHub

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

Jump to bottom
Closed
YourSandwich opened this issue Feb 14, 2024 · 6 comments
Closed

Full Freeze in one specific channel #27012

YourSandwich opened this issue Feb 14, 2024 · 6 comments
Labels
O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect

Comments

@YourSandwich
Copy link

Steps to reproduce

It's not easily reproducible since it happens in just one specific chat.

  1. Join The chat.
  2. Wait or Scroll

Both users are on the same server.
I believe the first time it happened was about 4 months ago, when the sender sent a voice message.

This does not Happen on Element X

Outcome

Element Desktop Freezes completly with this stdout

Error getting the event index passphrase out of the secret store [Error: The name is not activatable]
Invalid SOS parameters for sequential JPEG
Invalid SOS parameters for sequential JPEG

<--- Last few GCs --->

[1:0x34dc30c94000]     1645 ms: Mark-Compact (reduce) 404.7 (428.1) -> 243.0 (249.1) MB, 102.99 / 0.00 ms  (average mu = 0.936, current mu = 0.799) last resort; GC in old space requested
[1:0x34dc30c94000]     1804 ms: Mark-Compact (reduce) 243.0 (249.1) -> 243.0 (247.9) MB, 159.14 / 0.00 ms  (average mu = 0.785, current mu = 0.000) last resort; GC in old space requested


<--- JS stacktrace --->

[199078:0214/231511.530936:ERROR:v8_initializer.cc(789)] V8 javascript OOM (CALL_AND_RETRY_LAST).

Operating system

Arch Linux

Application version

Element Nightly version: 2024021401 Crypto version: Olm 3.2.15

How did you install the app?

https://aur.archlinux.org/packages/element-desktop-nightly-bin

Homeserver

https://archworks.co | Synapse 1.101.0

Will you send logs?

Yes
@YourSandwich
Copy link
Author

The Issue is with the RoomID !WAxBAeiOXmflFgjefd:archworks.co

@YourSandwich
Copy link
Author

This also happens on the Stable Client

Element version: 1.11.57
Crypto version: Olm 3.2.15

@dbkr dbkr added S-Major Severely degrades major functionality or product features, with no satisfactory workaround O-Uncommon Most users are unlikely to come across this or unexpected workflow labels Feb 26, 2024
@YourSandwich
Copy link
Author

Nothing changed. I can manage to keep the client working as long as i don't scroll up sometimes.
This happens only on Element Desktop Client.

@YourSandwich
Copy link
Author

Same result on Windows. Other clients like Cinny, Fractal, Fluffychat are unaffected.

@YourSandwich
Copy link
Author

Can I get some tips on debugging this? Maybe I could delete some unimportant events that are maybe causing this?

One specific thing about this DM Room is, it has Gigabytes of Voice Messages and other Media.

@t3chguy
Copy link
Member

t3chguy commented Apr 18, 2024

Duplicate of #26239

@t3chguy t3chguy marked this as a duplicate of #26239 Apr 18, 2024
@t3chguy t3chguy closed this as not planned Won't fix, can't repro, duplicate, stale Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dbkr @t3chguy @YourSandwich