What is chrome_crashpad_handler, and why is it running on my Mac?
Last reviewed: 19 November 2026. Locations checked in Google Chrome 157 and in an Electron app on macOS 26.3.1.
chrome_crashpad_handler is the Crashpad crash reporter that Google Chrome, and apps built on Electron, start alongside themselves. It waits in the background and, when one of the app's processes crashes, takes a snapshot of it, writes a crash report to disk and, if you allowed it, uploads the report. It uses almost no CPU unless something is crashing.
chrome_crashpad_handler at a glance
| chrome_crashpad_handler | |
|---|---|
| Made by | Google (Crashpad, used by Chrome and by Electron apps) |
| Type | Crash reporter helper |
| Location | /Applications/Google Chrome.app/Contents/Frameworks/Google Chrome Framework.framework/Versions/[version]/Helpers/chrome_crashpad_handler |
| Runs as | your user |
| Can you quit it? | Yes, but crashes of the app it watches are no longer recorded until the app is restarted. |
What is chrome_crashpad_handler?
Crashpad is Google's open-source crash reporting system. Its design document says the handler runs in a separate process from the app it watches; on macOS the kernel sends crash exceptions to the handler directly, so no code has to run inside the crashing process. The handler suspends the crashed process, writes a minidump into a database, then lets it go.
Electron, the framework behind many desktop apps, also uses Crashpad, so you can see several chrome_crashpad_handler processes at once: one for Chrome and one for each Electron app. On this Mac, Discord's copy runs from Discord.app/Contents/Frameworks/Electron Framework.framework/Helpers/ with a crash database in ~/Library/Application Support/discord/Crashpad.
Is chrome_crashpad_handler safe?
Yes, when it runs from inside an app's own bundle. It only records crashes of processes that registered with it, and Crashpad's design says reports should never be uploaded without your consent. The full command line, shown by ps -o args= -p <PID>, includes --database= with the folder of the app it belongs to.
Why does chrome_crashpad_handler use so much CPU, disk, network and memory?
- An app crashing repeatedly. Each crash makes the handler read the crashed process's memory and threads and write a minidump. A renderer or helper that keeps crashing makes the handler busy over and over.
- Writing crash reports. Minidumps are written to the app's Crashpad database. Crashpad's database can be set to keep a limited number of dumps up to a size limit.
- Uploading reports. If crash reporting is on, the handler sends pending reports to the vendor's server. Crashpad's design limits uploads to one per hour.
- One handler per app. Each Chromium or Electron app starts its own handler, so several copies with small memory each are normal.
How much CPU is normal for chrome_crashpad_handler?
Typically near 0% CPU with a small amount of memory, for as long as its app is running. It wakes only to handle a crash or upload a report.
Seeing more than one chrome_crashpad_handler is normal when Chrome and Electron apps are open together.
How do you find which app a chrome_crashpad_handler belongs to?
- Read its command line. Run
ps -axo pid,args | grep crashpad_handlerin Terminal. The path and the--database=folder name the app that started it. - Look for the crashing app. If the handler is busy, an app is crashing. Check the app's crash dialogs and Console's Crash Reports, and update or reinstall that app.
- Turn off crash uploads in Chrome. In Chrome's settings, search for Help improve Chrome's features and performance and turn it off; its description says it sends usage statistics and crash reports to Google.
- Quit the app it belongs to. Quitting Chrome or the Electron app ends its handler. You do not need to stop the handler itself.
When should you worry about chrome_crashpad_handler?
Steady CPU use from a crash handler means something keeps crashing. Find the owning app from its command line and update it.
A chrome_crashpad_handler running from a folder that is not inside an app bundle, or not signed by the same developer as the app around it, is worth checking with codesign -dv --verbose=2.
How do you check chrome_crashpad_handler in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type chrome_crashpad_handler in the search field. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. The Network tab shows its Sent Bytes and Rcvd Bytes. 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 chrome_crashpad_handler 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. nettop shows its live network traffic.
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'chrome_crashpad_handler' | grep -v grep
sudo fs_usage -w -f filesys <PID> # PID from the ps line above
nettop -p <PID> # PID from the ps line above
How can Thrum help with chrome_crashpad_handler?
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 chrome_crashpad_handler 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 chrome_crashpad_handler 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 chrome_crashpad_handler
Why is chrome_crashpad_handler running when Chrome is closed?
Electron apps include the same handler with the same name. Its path shows which app started it, such as Discord or Visual Studio Code.
Can I delete chrome_crashpad_handler?
No. It is part of the app's signed bundle, and changing the bundle breaks its signature. Turn off crash reporting in the app instead, if it offers the setting.