element-desktop icon indicating copy to clipboard operation
element-desktop copied to clipboard

Performance degradation after high app uptime

Open rom4nik opened this issue 2 years ago • 6 comments

Steps to reproduce

  1. Launch app
  2. Use it, scroll through timeline, click on rooms, etc. - all relatively smooth
  3. Minimize app to system tray, leave PC running for 24h
  4. Come back, use app as in step 2

Outcome

What did you expect?

Same performance as in step 2 above.

What happened instead?

Slow reaction to input, low framerate during scrolling, etc. Here's a video where after initial pointer circling I'm continuously scrolling:

https://github.com/vector-im/element-desktop/assets/46846000/18524a84-768a-4d5b-bd49-190707a5859d

I tried to export traces from Performance tab in Electron devtools, collected while recording video above, but it failed silently or produced empty files. I have a few screenshots from the results:

Screenshot_20230728_193740 Screenshot_20230728_193801 Screenshot_20230728_193807 Screenshot_20230728_193815

I'm running up to date Arch Linux with KDE Plasma, Xorg and proprietary Nvidia drivers. FWIW, I've never had this issue on another machine with Intel iGPU (but otherwise similar setup of Arch and KDE).

Operating system

Arch Linux

Application version

Element 1.11.36, Olm 3.2.14

How did you install the app?

https://archlinux.org/packages/extra/x86_64/element-desktop/

Homeserver

Synapse 1.88.0

Will you send logs?

Yes

rom4nik avatar Jul 28 '23 18:07 rom4nik

My report in #1131 is almost certainly a duplicate of that. I saw the same 200-300ms "long task" warning spans show up in Chrome_ChildIOThread once the process grew sluggish.

On my machine I'm using Ubuntu, with i3 -- but I am using the proprietary NVIDIA drivers on both machines where I see it! The cards I have are:

  • 01:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] (rev a1)
  • 09:00.0 VGA compatible controller: NVIDIA Corporation GP108 [GeForce GT 1030] (rev a1)

Now that you've mentioned it, I don't recall that I've ever seen this happen on my laptop, which is the same (Ubuntu, i3) except it has an Intel GPU...

jclulow avatar Aug 04 '23 00:08 jclulow

The same on AMD GPU and ryzen CPU on Arch Linux, 12gen intel mobile cpu + gpu on Arch Linux and even on M1 Macbook Pro on MacOS 12 6.6. Element starts using big amount of RAM and makes the computer and himself slower. Probably just needs to cleanup the internal structures and should be much better.

It can be other issue tho as I've not debugged it, I just restart it when it feels bad ;)

JuniorJPDJ avatar Aug 04 '23 06:08 JuniorJPDJ

I'm necrobumping but opening another issue describing the same behavior is probably also not helping.

I have the same issue:

  • freezes with duration up to seconds
  • element process uses 100% CPU forever

My setup:

  • OS: Arch Linux x86_64
  • Host: 21HMS29W00 ThinkPad X1 Carbon Gen 11
  • Kernel: 6.6.56-1-lts
  • CPU: 13th Gen Intel i7-1365U (12) @ 5.200GHz
  • GPU: Intel Raptor Lake-P [Iris Xe Graphics]
  • Wayland compositor: hyprland 0.44.1-1
  • Version (element-desktop): 1.11.78-1
  • Command: element-desktop --enable-features=UseOzonePlatform --ozone-platform=wayland

br-olf avatar Oct 30 '24 09:10 br-olf

I don't know why this isn't high priority since it happens consistently every time Element stays open and seemingly has been this way for over a year now. One of my CPU Threads shoots up to 100% while the others go down. SchildiChat doesn't seem to have this issue and it uses less resources overall. Does anyone know the reason for this? Edit: SchildiChat also has the same problem apparently it just happened to take longer.

m1neral-rocks avatar May 05 '25 16:05 m1neral-rocks

@m2neral I switched to Cinny because of this issue. I really don't like recommending something else but the current situation with element is unbearable.

br-olf avatar May 07 '25 12:05 br-olf

This went away for me I think? I haven't seen this happen in a while.

m1neral-rocks avatar Jun 03 '25 20:06 m1neral-rocks