What is ReportCrash, and why is it using so much CPU on my Mac?
Last reviewed: 19 November 2026. Path, accounts, launchd jobs and man page checked on macOS 26.3.1.
ReportCrash is the macOS process that analyzes a crashing app or process and saves a crash report to disk. If it keeps using CPU, something on the Mac is crashing repeatedly, and ReportCrash is writing a report each time. Find the crashing program in Console's Crash Reports and update, fix or remove it.
ReportCrash at a glance
| ReportCrash | |
|---|---|
| Made by | Apple (part of macOS, crash reporting) |
| Type | Launch agent and system daemon |
| Location | /System/Library/CoreServices/ReportCrash |
| Runs as | your user |
| Started by | launchd job com.apple.ReportCrash |
| Can you quit it? | Yes, but launchd runs it again the next time something crashes. |
What is ReportCrash?
Its man page says ReportCrash "analyzes crashing processes and saves a crash report to disk" and that launchd invokes it automatically when a crash is detected. For apps and other processes in your session it runs as a launch agent (com.apple.ReportCrash) and saves reports in ~/Library/Logs/DiagnosticReports/. For daemons and other privileged processes it runs as a launch daemon (com.apple.ReportCrash.Root) and saves reports in /Library/Logs/DiagnosticReports, readable only by administrators.
For app crashes, it shows the dialog saying the app quit unexpectedly, with options to reopen it or send the report to Apple. The man page notes that reports sent to Apple are submitted by the SubmitDiagInfo process, and that older reports for a process that crashes too often are removed automatically to save disk space.
Is ReportCrash safe?
Yes. ReportCrash is part of macOS in /System/Library/CoreServices on the read-only system volume. Its activity is a symptom of a crash elsewhere, not a problem in ReportCrash.
Why does ReportCrash use so much CPU, disk and memory?
- A program crashing in a loop. A background agent or helper that crashes and is restarted by launchd crashes again, and each crash makes ReportCrash analyze the process and write a report. This is the most common reason it stays busy.
- Large crashing processes. Analyzing a crash means reading the crashed process's threads and loaded libraries. Big apps with many threads take longer.
- Writing reports. Each crash produces a report file. Console lists crash reports with the
.ipsextension. - Holding the crashed process's details. While it builds a report it keeps information about the crashed process in memory, so memory use rises briefly during a crash.
How much CPU is normal for ReportCrash?
Most of the time ReportCrash is idle or not running. A few seconds of CPU right after an app crashes is normal.
ReportCrash showing up again and again, or staying busy for minutes, means repeated crashes.
How do you stop ReportCrash from using so much CPU?
- Find what is crashing. Open Console (Applications > Utilities), click Crash Reports in the sidebar, and look for a name that appears many times with recent dates.
- Check the folders directly. In Finder, choose Go > Go to Folder and open
~/Library/Logs/DiagnosticReports. Many reports with the same name point to the culprit. - Update or reinstall that app. Install the latest version from its developer. If it is a helper of an app you no longer use, remove the app and its login items.
- Turn off a crashing login item. Open System Settings > General > Login Items & Extensions and turn off the item that belongs to the crashing app, so launchd stops relaunching it.
- Restart. A restart clears a temporary crash loop in a system component. If the same system process keeps crashing after a restart, install any pending macOS update.
When should you worry about ReportCrash?
ReportCrash at high CPU for many minutes, or appearing every few seconds, always means a crash loop. The crash reports tell you which program, and fixing that program fixes ReportCrash.
Repeated crashes of many unrelated apps can point to a damaged system or failing hardware; Apple Diagnostics is the next step in that case.
How do you check ReportCrash in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type ReportCrash in the search field. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. The Memory tab shows its Memory. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every ReportCrash process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). fs_usage prints each file it reads or writes until you press Control-C; it needs an administrator password.
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'ReportCrash' | grep -v grep
sudo fs_usage -w -f filesys ReportCrash
How can Thrum help with ReportCrash?
Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when ReportCrash is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. Click ReportCrash in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions about ReportCrash
Should I disable ReportCrash?
The man page documents launchctl commands that disable crash reporting, but doing so only hides the symptom. The crashing program still crashes, and you lose the reports that show why.
Where are Mac crash reports saved?
Reports for your apps are in ~/Library/Logs/DiagnosticReports/; reports for system processes are in /Library/Logs/DiagnosticReports. Console shows both under Crash Reports.
Does ReportCrash send data to Apple?
Only if you choose to send a report or have turned on Share Mac Analytics. The sending is done by SubmitDiagInfo.
Sources
- ReportCrash(8) man page: run man ReportCrash in Terminal
- Apple Support: Reports in Console on Mac