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.

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

Ballooning RAM usage on renderer process #24725

Open
b3noist opened this issue Mar 2, 2023 · 1 comment
Open

Ballooning RAM usage on renderer process #24725

b3noist opened this issue Mar 2, 2023 · 1 comment
Labels
A-Performance O-Occasional Affects or can be seen by some users regularly or most users rarely S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect

Comments

@b3noist
Copy link

b3noist commented Mar 2, 2023

Steps to reproduce

  1. Start Element
  2. Idle and/or change rooms occasionally for hours or days
  3. Renderer process goes from slightly over 200 MiB to hundreds higher
  4. Close and restart Element
  5. Renderer process is back to normal for the moment
  6. Repeat and watch RAM usage climb again

Outcome

What did you expect?

RAM usage to remain relatively stable or grow very slowly.

What happened instead?

RAM usage grows by hundreds in a single day doing next to nothing. The highest I've seen the renderer process go is slightly over 800 MiB, by which point I closed and restarted Element. I've also sometimes seen the main process grow over 500 MiB as well.

Operating system

Arch Linux, kernel 6.2.1-arch1-1, Sway 1.8.1

Application version

Element version: 1.11.20 Olm version: 3.2.12

How did you install the app?

element-desktop from package manager

Homeserver

No response

Will you send logs?

No
@florianduros
Copy link
Contributor

Maybe related to element-hq/element-desktop#680 about the excessive RAM usage

@florianduros florianduros added A-Performance S-Major Severely degrades major functionality or product features, with no satisfactory workaround O-Occasional Affects or can be seen by some users regularly or most users rarely labels Mar 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-Performance O-Occasional Affects or can be seen by some users regularly or most users rarely 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
2 participants
@florianduros @b3noist