Skip to content
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

App is crashing daily due to memory usage #25423

Closed
turt2live opened this issue May 23, 2023 · 3 comments
Closed

App is crashing daily due to memory usage #25423

turt2live opened this issue May 23, 2023 · 3 comments
Labels
A-Memory Memory leaks, leak hunting tools A-Performance 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

@turt2live
Copy link
Member

Steps to reproduce

I am making assumptions about the cause here, but here is the pattern for me:

  1. Have a relatively large account
  2. Use that account a lot throughout the day (lots of encrypted rooms)
  3. Immediately after changing rooms, client crashes randomly (blank screen); Memory usage drops to basically nothing.
  4. Quit the app from the task tray
  5. Reopen app, and repeat.

Outcome

What did you expect?

Not crashing.

What happened instead?

Blank screen after 6-8 hours of using the app. Sometimes as few as 2-4 hours. Appears to be related to how many rooms I click through to read messages in. Most of those rooms (90%) are encrypted with plenty of devices, however I only speak in about a dozen of them.

I'm in 3678 rooms (3399 visible) as of writing.

Unfortunately, getting a memory profile is difficult because the act of doing so often pushes the VM over the limit and crashes due to OOM. By the time I can get a profile after startup, the process is dangerously close to crashing while it tries to interpret the profile it just took.

The memory behaviour is a relatively steep cliff at startup: the OS reports Element using 2.6gb with only 60 seconds of uptime, but it still takes several hours for it to finally fill the gap to the point where it can crash due to memory pressure. Meanwhile, it takes 15-20 minutes for my CPU fan to stop spinning after startup, which I believe is the "decrypt all the rooms" loop running.

Operating system

Windows 11

Application version

Element Nightly version: 0.0.1-nightly.2023052201 Olm version: 3.2.14

How did you install the app?

The Internet

Homeserver

t2l.io

Will you send logs?

Yes

@andybalaam andybalaam 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 A-Memory Memory leaks, leak hunting tools A-Performance labels May 23, 2023
@andybalaam
Copy link
Contributor

Related: #25264

@Johennes
Copy link
Contributor

I think this is more or less a duplicate of element-hq/element-desktop#680?

@t3chguy
Copy link
Member

t3chguy commented May 23, 2023

Duplicate of element-hq/element-desktop#680

@t3chguy t3chguy marked this as a duplicate of element-hq/element-desktop#680 May 23, 2023
@t3chguy t3chguy closed this as completed May 23, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Memory Memory leaks, leak hunting tools A-Performance 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
Development

No branches or pull requests

4 participants