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

Spike in CPU usage on Intel when upgrading to 2.3.8 and using a virtual screen #3154

Closed
nuTTeLLo opened this issue Jul 2, 2024 · 6 comments
Assignees
Labels
bug Something isn't working done All tasks are completed Intel Related to Macs with Intel architecture released Released
Milestone

Comments

@nuTTeLLo
Copy link

nuTTeLLo commented Jul 2, 2024

There is a huge spike in CPU usage when upgrading from 2.3.7 to 2.3..8.

Notice that the WindowServer process CPU usage goes up to 300-400% and the colorsync.useragent process suddenly just starts going up to 40-50% CPU usage when using 2.3.8. This makes the computer almost unusable. Was never this issue on 2.3.7 (WindowServer process generally around the below 100% CPU usage mark).

Using a 2019 Macbook Pro with two attached monitors and an Virtual Screen mirrored to an iPad.

@vincetran96
Copy link

vincetran96 commented Jul 2, 2024

There is a huge spike in CPU usage when upgrading from 2.3.7 to 2.3..8.

Notice that the WindowServer process CPU usage goes up to 300-400% and the colorsync.useragent process suddenly just starts going up to 40-50% CPU usage when using 2.3.8. This makes the computer almost unusable. Was never this issue on 2.3.7 (WindowServer process generally around the below 100% CPU usage mark).

Using a 2019 Macbook Pro with two attached monitors and an Virtual Screen mirrored to an iPad.

How long did the spike last? I have been experiencing huge, short (about 1-2 seconds) spikes in CPU usage recently, after installing and trying BetterDisplay, among some other apps. As I'm not sure which app has been causing the spikes, I have tried quitting all of my recently installed ones, except BetterDisplay, and still got those spikes. This led me to the issue tracking page and I just found this one.

If if matters, my hardware is

  • Macbook Pro 14" 2021
  • CPU: Apple M1 Pro
  • OS: MacOS Sonoma 14.5

BetterDisplay version: 2.3.8

@waydabber
Copy link
Owner

Hi @nuTTeLLo,

sorry about the issue with the virtual screen. Some questions:

  • If you start the app with logging from Terminal, do you see any special continuous activity/log output? /Applications/BetterDisplay.app/Contents/MacOS/BetterDisplay -v
  • Does this issue go away if you downgrade to v2.3.7?

The only colorsync related change in v2.3.8 was #3137. The change however should not cause a sustained CPU usage in colorsync.useragent.

@vincetran96 - you should check Activity Monitor and see which apps are causing the spike. One rare reason how it could be related to BetterDisplay is the XDR upscaling feature, which puts the screen into EDR (HDR) mode for extra brightness. If auto brightness (ambient light sensor) is enabled and the brightness conditions vary, this can cause extra CPU usage on some apps as the system might ask various apps to re-tonemap HDR content as the brightness changes. If this happens continually, that puts some extra burden on these apps. To avoid this, you can use native XDR upscaling (select the BetterDisplay XDR preset under XDR Presets & Brightness) instead of the default software XDR upscaling or simply turn off auto brightness (or disable software XDR upscaling).

@waydabber waydabber changed the title Huge spike in CPU usage when upgrading to 2.3.8 Spike in CPU usage on Intel when upgrading to 2.3.8 and using a virtual screen Jul 2, 2024
@waydabber waydabber added bug Something isn't working Intel Related to Macs with Intel architecture labels Jul 2, 2024
@waydabber
Copy link
Owner

@nuTTeLLo - are you on Ventura or Sonoma?

@waydabber
Copy link
Owner

Nvm, was able to reproduce the issue on Intel Macs both on Ventura and Sonoma. Apparently simply enabling a virtual screen will trigger and endless ColorSync repository update cycle on Intel. :(

I'll fix this issue in an update.

@waydabber waydabber added in progress Implementing internal pre-release Enable internal pre-releases under Settings/Applications/Updates and removed awaiting response from issue reporter Needs further info labels Jul 2, 2024
@waydabber waydabber self-assigned this Jul 2, 2024
@waydabber waydabber added this to the v2.3.8 milestone Jul 2, 2024
@waydabber waydabber added done All tasks are completed and removed in progress Implementing labels Jul 2, 2024
@waydabber waydabber modified the milestones: v2.3.8, v2.3.9 Jul 2, 2024
@waydabber waydabber added released Released and removed internal pre-release Enable internal pre-releases under Settings/Applications/Updates labels Jul 2, 2024
@waydabber
Copy link
Owner

I posted a v2.3.9 update as this issue seems to be a severe one that potentially affects many Intel configurations.

@Adrian-at-IB
Copy link

Thanks for the quick fix. Works well with 2.3.9.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working done All tasks are completed Intel Related to Macs with Intel architecture released Released
Projects
None yet
Development

No branches or pull requests

4 participants