iOS 26.1 Simulator in Xcode 26.1 makes ReportCrash process run at 60-160% of CPU

My MBP M1 Pro gets really hot. iOS 26.1 Simulator in Xcode 26.1 makes ReportCrash process run at 60-160% of CPU shows Activity Monitor.

MacOS 26.1. I've reported this via Feedback Assistant: FB*****09.


Is there a way to quit this process permanently? When I Force Quit this it opens again immediately. Only way to stop it is to quit Simulator. But then again, I need to use the Simulator.


[Edited by Moderator]

Posted on Nov 4, 2025 10:53 AM

Reply
Question marked as Top-ranking reply

Posted on Nov 6, 2025 9:19 AM

I have the exact same issue, this occurs when for example your preview crashes for any reason, ReportCrash stays on forever. My fans were really loud for no reason and stayed loud longer, I was wondering what was causing it. This was never an issue before and preview could crash multiple times. This is Xcode 26.1 exclusive.


I had to disable crash reporting entirely.


launchctl unload -w /System/Library/LaunchAgents/com.apple.ReportCrash.plist

sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.ReportCrash.Root.plist


You can then re-enable with the same commands just instead of unload call load.

10 replies
Question marked as Top-ranking reply

Nov 6, 2025 9:19 AM in response to mallow_pl

I have the exact same issue, this occurs when for example your preview crashes for any reason, ReportCrash stays on forever. My fans were really loud for no reason and stayed loud longer, I was wondering what was causing it. This was never an issue before and preview could crash multiple times. This is Xcode 26.1 exclusive.


I had to disable crash reporting entirely.


launchctl unload -w /System/Library/LaunchAgents/com.apple.ReportCrash.plist

sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.ReportCrash.Root.plist


You can then re-enable with the same commands just instead of unload call load.

Nov 6, 2025 11:09 AM in response to Markusuv

Thank you! You're a lifesaver. I can work again :)

One thing... ChatGPT suggested I use those commands without the "-w" flag. This way it's not permanent and those services will run again after reboot. I prefer this as I'm worried I will forget to load them again in the future after Apple hopefully fixes this in the next Xcode.


So I'm using these commands:

launchctl unload /System/Library/LaunchAgents/com.apple.ReportCrash.plist
sudo launchctl unload /System/Library/LaunchDaemons/com.apple.ReportCrash.Root.plist

Nov 6, 2025 12:16 AM in response to Mac Jim ID

Both Home Screen and with an app running. Sometimes it’s 60%, sometimes it’s up to 160%.

In another thread I’ve seen it’s probably because Simulator background not loading and crashing. And I can confirm my Simulator doesn’t show background wallpaper.


However, iOS 26.0 Simulator has the wallpaper. And the CrashReport process is still running hot.


The problem started on Xcode 26.1. Xcode 26.0 didn’t have this issue.

Nov 4, 2025 11:18 AM in response to mallow_pl

I checked on a machine that was still using 26.0.1, and the ReportCrash process was using 30%-50% with the Simulator, so I then checked on my machine that had been updated to MacOS 26.1 along with Xcode and the 26.1 Simulator and the results were the same 30%-50%.


Are you seeing this with the Simulator on the Home Screen, or only when running an app in the Simulator? I checked both with a launched template app in the Simulator and when just viewing the Simulator on the Home Screen.

iOS 26.1 Simulator in Xcode 26.1 makes ReportCrash process run at 60-160% of CPU

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.