amiantos/lifesaver

High CPU Usage by legacyScreenSaver Process on MacBook M1 After Sonoma 14.X Update

Opened this issue · 5 comments

HoBeom commented

Environment:

  • Device: MacBook M1
  • OS: Sonoma 14.X
  • Application: LifeSaver Screen Saver

Issue Description:
After updating my MacBook M1 to Sonoma 14.X, I've started experiencing an issue with the LifeSaver screen saver causing excessive CPU usage. Specifically, the legacyScreenSaver process consumes over 100% CPU. This issue began immediately following the OS update.

Steps to Reproduce:

  1. Update the MacBook M1 to Sonoma 14.X.
  2. Use LifeSaver as the screen saver.
  3. Observe the legacyScreenSaver process's CPU usage in Activity Monitor.

Expected Behavior:
The legacyScreenSaver process should not consume excessive CPU resources, allowing the screen saver to run smoothly without impacting system performance.

Actual Behavior:

  • The legacyScreenSaver process exceeds 100% CPU usage when the LifeSaver screen saver is active.
  • Restarting the MacBook and changing the screen saver temporarily resolves the issue, but it reoccurs when switching back to LifeSaver.
  • It appears that the screen saver might be causing the legacyScreenSaver process to persistently use CPU resources in the background, even when not active. Additionally, entering the screen saver seems to compound the CPU usage each time, suggesting possible resource allocation or release issues.

Troubleshooting Steps Taken:

  • Changed the screen saver to default
  • Restarted the MacBook M1 or kill process 'legacyScreenSaver-x86_64'

Request:

  • Could the compatibility of LifeSaver with Sonoma 14.X on MacBook M1 be investigated?
  • Is this issue observed on other Mac models, particularly those not using Intel processors?

Additional Information:

  • This problem was not present before the Sonoma 14.X update, indicating a potential compatibility issue with the new OS version.

Thank you for your attention to this matter. I look forward to any updates or suggestions for resolving this issue.

SCR-20240228-qigr

amiantos commented

I think all legacy screensavers have issues in Sonoma, but maybe I'm wrong. I'll look around to see what I can find. I would be surprised if Apple doesn't remove legacy screensaver support at some point but that depends on them releasing the new screensaver framework and they haven't...

amiantos commented

A quick google indicates this is a widespread issue with screensavers in Sonoma :(

amiantos commented

In case someone else lands here, allegedly there is an open radar for this: FB13041503. Not sure how to look it up myself at the moment to see what the deal is.

HoBeom commented

Thank you for your quick comments.
I've tested your other screensaver, multiclock, and it doesn't exhibit the same high CPU usage issue.
This makes me wonder if the underlying codebase or implementation between LifeSaver and multiclock differs in a way that affects how they interact with the Sonoma update.
Could this observation provide any insight or potential direction for troubleshooting the high CPU usage issue with LifeSaver?

amiantos commented

Thank you for your quick comments. I've tested your other screensaver, multiclock, and it doesn't exhibit the same high CPU usage issue. This makes me wonder if the underlying codebase or implementation between LifeSaver and multiclock differs in a way that affects how they interact with the Sonoma update. Could this observation provide any insight or potential direction for troubleshooting the high CPU usage issue with LifeSaver?

Hmm, good idea. I thought Multiclock did it too, but I'll test them both out and see how it goes. I know that as I learned more, I built the screensavers a bit differently, so you might be right that there is something I can fix. I have another screensaver, Ealain, that is built much differently from the others and I think it exhibits the same issue, so I've been assuming it's just all screensavers. But maybe it isn't...

I'll look into it!

  • ❤️2