My laptop is warm/hot to touch as a result of it.
Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load
11–20 of 145 posts
Re: Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load
#12Can't reproduce this on macOS Ventura 13.6 on a Mac Studio.
Re: Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load
#13Off topic: I wish someone would do this kind of analysis to determine why Microsoft Teams helper process is always at 50-70% CPU load on my M-Based MacBook Pro. My laptop is warm/hot to touch as a result of it.
Re: Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load
#14Can't reproduce this on macOS Ventura 13.6 on a Mac Studio.
13.6 on my M2 MacBook air: 0,8 tot 1,1 when idle, not using.
Re: Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load
#15Re: Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load
#16This is such a classic UI programming bug, and almost every UI programming framework has a way to achieve this accidentally using core components. React is notorious for this, but even in non-declarative frameworks it's very easy to get a reactivity loop on a trigger or model update and do this.
Re: Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load
#17Re: Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load
#18That's probably a good amount of battery life that can be claimed back once this is fixed
The fix will be ready for the next macOS Apple Event so that they can claim battery performance improvements
Re: Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load
#19What does "even though there is no UI visible" mean?
Control Center is an overlay that is only shown when the appropriate icon in the menu bar is clicked. https://support.apple.com/guide/mac-help/mchl50f94f8f/13.0/m...
Or when the mouse starts entering the target before the click at least?
Re: Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load
#20Is Swift UI the problem here? Sounds like the compositor or equivalence isn't doing its job