Thrum

What is CrashReporterSupportHelper on my Mac?

Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.

CrashReporterSupportHelper is a small macOS daemon that provides functionality to Apple's CrashReporterSupport framework through an XPC service. It starts on demand when crash reporting code needs it and uses little CPU or memory. It is part of macOS and needs no action.

CrashReporterSupportHelper at a glance

CrashReporterSupportHelper
Made byApple (part of macOS, crash reporting)
TypeSystem daemon (XPC service)
Location/System/Library/CoreServices/CrashReporterSupportHelper
Runs asroot
Started bylaunchd job com.apple.CrashReporterSupportHelper
Can you quit it?Yes, but launchd starts it again on demand.

What is CrashReporterSupportHelper?

The man page says CrashReporterSupportHelper "provides functionality to the CrashReporterSupport framework by way of an XPC service." Apple does not document the individual functions. Given its name and the framework it serves, it is part of the same crash reporting system as ReportCrash and osanalyticshelper.

It runs as root from the com.apple.CrashReporterSupportHelper launchd job, which registers a service that other processes connect to; launchd starts it the first time one of them does.

Is CrashReporterSupportHelper safe?

Yes. It is part of macOS in /System/Library/CoreServices on the read-only system volume. About 1 MB of memory was observed on this Mac.

Why does CrashReporterSupportHelper use so much CPU and memory?

How much CPU is normal for CrashReporterSupportHelper?

Near 0% CPU and about a megabyte of memory. It may or may not be running at any given time.

How do you stop CrashReporterSupportHelper from using so much CPU?

  1. Check for a crash loop. Open Console and look at Crash Reports. If one program has many recent reports, fix or remove it.
  2. Watch ReportCrash too. If ReportCrash is also busy, follow the steps on its page; this helper is busy for the same reason.
  3. Restart. If it stays active with no crashes happening, restart the Mac.

When should you worry about CrashReporterSupportHelper?

Sustained CPU from this helper is not expected; it usually means something is crashing repeatedly.

A process with this name outside /System/Library/CoreServices would not be Apple's.

How do you check CrashReporterSupportHelper in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type CrashReporterSupportHelper in the search field. The CPU tab shows its % CPU. 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 CrashReporterSupportHelper process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'CrashReporterSupportHelper' | grep -v grep

How can Thrum help with CrashReporterSupportHelper?

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 CrashReporterSupportHelper 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. macOS does not let apps quit processes owned by root or other users, so Thrum shows them for information and leaves stopping them to the steps above.

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 CrashReporterSupportHelper

Can I delete CrashReporterSupportHelper?

No. It is on the read-only system volume, which macOS protects, and crash reporting depends on it.

Does it send crash reports to Apple?

Its man page describes only support functions for the crash reporting framework. Sending reports to Apple is SubmitDiagInfo's job and follows your analytics settings.

Sources