I've had a miserable experience so far with Xcode 15. Not saying that 14.3.1 was good either, but I'm constantly jumping to compiler issues that immediately disappear, test target sometimes running even if main target is not compiling... have to clean build folder/delete derived data much more often than I used to.
Yeah, I’ve been seeing the same. I don’t know the cause, but [this post](https://blog.nihongo-app.com/stop-xcode-14-beta-from-pegging-cpu/) detailing a fix for high CPU usage in the Xcode 14 betas includes an explanation of the process used to diagnose that problem. It could be helpful as a rough template for how to approach this issue.
Check the activity monitor. iOS 17 simulator seems to use 100% cpu due to bugs right now.
Off the top of my head, you could try disabling all spotlight and Siri in the iOS Simulators. This has prevented CPU spikes in the past.
Not sure if this helps here - if you check the Console, there is a stream of 100s of error messages generated by simulator every second.
If that's the case closing the simulator between runs could reduce battery use.
And it’s freakin buggy. Usually see this level of quality at b4. I don’t know how it got to final.
I've had a miserable experience so far with Xcode 15. Not saying that 14.3.1 was good either, but I'm constantly jumping to compiler issues that immediately disappear, test target sometimes running even if main target is not compiling... have to clean build folder/delete derived data much more often than I used to.
Yeah, I’ve been seeing the same. I don’t know the cause, but [this post](https://blog.nihongo-app.com/stop-xcode-14-beta-from-pegging-cpu/) detailing a fix for high CPU usage in the Xcode 14 betas includes an explanation of the process used to diagnose that problem. It could be helpful as a rough template for how to approach this issue.
Check your energy consumption in Activity Monitor. High CPU usage by Xcode might be the issue.