-
Notifications
You must be signed in to change notification settings - Fork 356
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
Comments
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
BetterDisplay version: 2.3.8 |
Hi @nuTTeLLo, sorry about the issue with the virtual screen. Some questions:
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 |
@nuTTeLLo - are you on Ventura or Sonoma? |
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. |
I posted a v2.3.9 update as this issue seems to be a severe one that potentially affects many Intel configurations. |
Thanks for the quick fix. Works well with 2.3.9. |
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.
The text was updated successfully, but these errors were encountered: