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

Wire desktop on Mac is using 30% continuous cpu #7771

Open
DrWhax opened this issue Apr 14, 2024 · 2 comments
Open

Wire desktop on Mac is using 30% continuous cpu #7771

DrWhax opened this issue Apr 14, 2024 · 2 comments

Comments

@DrWhax
Copy link

DrWhax commented Apr 14, 2024

Wire version: 3.35.4861
Operating system: Sonoma 14.3
Which antivirus software do you have installed: None

What steps will reproduce the problem?

  1. Open Wire App on MacOS
  2. Open htop
  3. 30% continuous cpu usage

What is the expected result?

Not burning through my battery due to the 30% CPU continuous usage

What is the actual result?

30% of my cpu cores are doing, something, with Wire, although i;m not entirely sure what.

Please provide any additional information below. Attach a screenshot if possible.

Screenshot 2024-04-14 at 22 58 57

Through profiling using Instruments I see that it's mostly busy in Electron's get_async_id()

Screenshot 2024-04-14 at 23 02 16

--verbose-logging doesn't show useful unfortunately, do let me know what I can do to help debug this further!

@DrWhax
Copy link
Author

DrWhax commented Jun 25, 2024

I'd still be very interested in seeing this be resolved! :)

@Siguza
Copy link

Siguza commented Oct 23, 2024

Just noticed this as well, on macOS 14.7 (23H124). Reminds me a lot of #2507.

Using --devtools, I was able to narrow the issue down to the subtree of #message-list element in #wire-main-app.
If you remove the transition: width .35s var(--ease-out-quart) property from #message-list and set .message-body to display: none, the high CPU usage disappears entirely. I didn't investigate what in the subtree of .message-body contributes to this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants