Abnormal use of CPU when idle

[JasonMahdjoub]

Steps to reproduce

Hi,
My system is Ubuntu 21.04, Linux 5.17.3, Gnome Shell 40, Wayland, Element version 1.10.9

When I let the element-desktop window opened, element use one CPU core at around 10% of usage. If I close the Element window, but without closing it which remains available into the system icons, than the CPU slow down around 0% of usage.
I have tried it into another computer with the same configuration, but with an older version of element-desktop (probably 1.10.8), and the problem does not occur. Then, I have updated Element to version 1.10.9, and the problem restarted to appear.
I have also tried Element-desktop into Windows, and the problem is the same.

Outcome

What did you expect?

0% of CPU usage

What happened instead?

10% of CPU usage

Operating system

Ubuntu 21.04, Windows 11

Application version

1.10.9

How did you install the app?

https://element.io/get-started

Homeserver

1.56

Will you send logs?

No

[dbkr]

Debug logs may tell us what's going on, so if anyone experiencing this problem is willing to submit some that may help to diagnose this. Otherwise we'll have to wait until it happens to somehow who's able to get a javascript profile.

[hsiktas]

I am affected by this and submitted debug logs from within the app while referencing this issue.

[goodboy]

I already reported this in the desktop room but the issue for me appears to be the electron17 child proc with the --type=renderer:

ps h gives the following cmd line for that child:

/usr/lib/electron17/electron --type=renderer --enable-crashpad --enable-crash-reporter=c199195c-d538-41e5-a910-3cec1cdc045d,no_channel --user-data-dir=/home/goodboy/.config/Riot --standard-schemes=vector --enable-sandbox --secure-schemes=vector --bypasscsp-schemes --cors-schemes --fetch-schemes=vector --service-worker-schemes --streaming-schemes --app-path=/usr/lib/element/app.asar --lang=en-US --num-raster-threads=2 --enable-main-frame-before-activation --renderer-client-id=4 --launch-time-ticks=77979922590 --shared-files=v8_context_snapshot_data:100 --field-trial-handle=0,11337240959077112874,7156202190314880840,131072 --enable-features=WebRTCPipeWireCapturer --disable-features=HardwareMediaKeyHandling,MediaSessionService,PlzServiceWorker,SpareRendererForSitePerProcess

This is on an arch install fwiw and strace-ing the proc shows spinning between futex, mprotect, getrandom and madvise 🤷🏼

In my case this is burning a whole core out of the 4 i have on that machine..

[dbkr]

Unfortunately not much in the log, and the renderer process is just the process that electron runs the app code in, so that's unsurprising. However, it looks like the little animated blue dots on the reply button might have something to do with this, and I suspect they may be animating even when the toolbar isn't visible.

[dbkr]

An illustrative gif:

[dbkr]

Oh, one more thing: if this is the case then a workaround would be to enable the threads beta which will stop the little blue dot from appearing. This probably explains why none of us are seeing this (we all turned threads on).

[hsiktas]

Confirmed! Turning on the Threads beta hides that blue dot, and the CPU usage goes down.

[catscratchedme]

I've also enabled threads beta, and my scrolling still seems laggy on Element desktop, especially when initially scrolling up in the timeline.