Crashpad Handler on Mac: CPU and crash reports

What crashpad_handler does

The Chromium project documents Crashpad’s handler as an exception-handling server: it catches exceptions, writes crash reports and can upload them to a collection server. The application using Crashpad controls its reporting behavior. A helper waiting for events can exist while its app is working normally.

Names vary. On the checked Mac, the process list included chrome_crashpad_handler inside Google Chrome, Claude and Visual Studio Code, and browser_crashpad_handler inside ChatGPT. These were observations from macOS 27.0.1 on 23 October 2026, not an exhaustive list of apps that use it.

Each observed helper ran in the signed-in account. Its enclosing app bundle identified its owner. This is why seeing more than one Crashpad row does not mean Chrome has secretly installed several separate crash reporters elsewhere.

Find which app owns the copy

1. Open Activity Monitor and choose View › All Processes. Search for crashpad.
2. Inspect each result separately. Check its User, CPU and process information rather than adding every matching row together.
3. Look at the executable path. The checked Chrome helper lived inside /Applications/Google Chrome.app/Contents/Frameworks/; other copies lived inside their own app bundles.
4. Save work and quit the owning app normally if you are testing whether its helper settles or exits. Reopen it and observe the same copy again.

The enclosing app is more informative than the word “chrome” in a helper name. An app built with Electron can include the same kind of component without being Google Chrome itself. A name alone is also not an authenticity check; an unexpected executable outside a recognizable app requires separate investigation.

If the helper uses a lot of CPU

Repeated crashes are one possible reason for repeated reporting work. Check whether the owning app is visibly closing, relaunching, losing tabs or displaying an error. A high reading without that evidence does not prove a crash loop. Writing or processing reports can also be distinct from the original app failure.

Use the app’s update and troubleshooting workflow first. For Chrome, save tabs you need, update the browser and investigate a repeatable page or extension problem. If Chrome itself is the busy component, Google Chrome Helper explains how to connect browser work to tabs. Do not remove Crashpad files as a substitute for fixing the app that keeps failing.

If a helper remains persistently busy after the app is current, collect a sample through Activity Monitor › More › Sample Process. Note which executable you selected and what action triggered the issue. Reports are more useful when the developer can reproduce the failure.

Crash collection and upload are different

Crashpad’s own documentation says uploads are disabled by default at the library level and must be enabled by the client app. That does not tell you the setting chosen by every application that integrates it. Do not assume a running helper proves that data is being sent, or that disabling upload removes the helper.

In current Chrome help, the user control is Chrome › Settings › You and Google › Google services › Help improve Chrome’s features and performance. Google says crash reports can include personal information, including memory related to the crash. Read its description before choosing whether to send reports.

Other apps have their own diagnostic and privacy settings. A Chrome setting does not configure the Crashpad component inside another app. On a managed browser, organizational policy may control reporting; ask your administrator if the choice is unavailable.

Should you delete or disable it?

Leave a working app’s bundled helper in place. Removing individual components can leave the application incomplete and may simply be undone by an update. If you no longer want the app, remove the whole app using its documented uninstall procedure. The Chrome removal guide starts with bookmarks, passwords and profile data.

A startup entry and a crash-reporting helper are different things. If an app reopens at login and starts its helper, manage the app’s login behavior in the startup items workflow. Do not disable unrelated system services or delete shared folders to hide a process name.

Where Tend fits

Tend’s free app view groups helpers by the outermost app bundle in their executable path. The observed Chrome, Claude, ChatGPT and Visual Studio Code helpers therefore fold into their respective apps, rather than appearing as four independent Crashpad apps. This grouping was checked in the source; it does not infer the owner of an arbitrary helper outside an app bundle.

Free CPU, memory and estimated watts help you identify the busy app. Free energy history covers 24-hour totals; Pro extends totals to 7 and 30 days. To inspect the individual helper, use Activity Monitor and its process reference.

Questions

Related guides

Sources

• Chromium, Crashpad handler manual and Chrome crash reporting.
• Google, automatic error and crash reporting.
• Local read-only process owners and executable paths, macOS 27.0.1, 23 October 2026; Tend helper grouping checked in ProcessMonitor.swift.
• Apple, Sample Process and diagnostic reports.

Sources checked 23 October 2026. Spotted something out of date? Tell us and we'll fix it.