What is spindump, and why is it using so much CPU on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
spindump is the macOS tool that records what every process on the Mac is doing, used to write a report when an app stops responding or is force quit. It samples call stacks across the whole system for a few seconds, so it causes a short, sharp CPU spike. It is part of macOS; frequent spindump activity means apps are hanging.
spindump at a glance
| spindump | |
|---|---|
| Made by | Apple (part of macOS) |
| Type | System daemon and command-line tool |
| Location | /usr/sbin/spindump |
| Runs as | root |
| Started by | launchd job com.apple.spindump |
| Can you quit it? | Yes, but it runs again the next time an app hangs or is force quit. |
What is spindump?
The man page says spindump "is used by various system components to create reports when an unresponsive application is force quit" and stores them in /Library/Logs/DiagnosticReports/. When run by hand it "samples user and kernel callstacks for every process in the system", which is why it is expensive for the few seconds it runs. Console lists these as Spin Reports with the .spin extension.
It runs as root from the com.apple.spindump launchd job. Activity Monitor uses the same mechanism: its More menu (the ellipsis button) has a Spindump option that Apple describes as creating a report for unresponsive apps that were terminated using force quit.
Is spindump safe?
Yes. spindump is part of macOS in /usr/sbin on the read-only system volume. Its CPU spike is the cost of taking a snapshot of every process and is over quickly.
Why does spindump use so much CPU, disk and memory?
- An app stopped responding. When an app hangs (the spinning wait cursor) or you force quit it, macOS collects a spin report so the cause can be diagnosed.
- Sampling every process. Capturing call stacks for all processes and the kernel, then symbolicating them into function names, is heavy work for a few seconds.
- Writing the report. Spin reports include a binary copy of the data at the end so they can be re-reported, and are saved to
/Library/Logs/DiagnosticReports/. - Holding samples. Samples for every process are kept in memory until the report is written, so memory use rises for a moment.
How much CPU is normal for spindump?
Usually idle. A spike of high CPU lasting a few seconds after an app hangs or is force quit is normal.
Frequent spindump spikes mean frequent hangs; the reports say which app.
How do you stop spindump from using so much CPU?
- Find the app that hangs. Open Console, click Spin Reports, and look at which app names appear most.
- Update that app. Install the latest version. Hangs that are fixed by the developer stop generating spin reports.
- Check memory pressure. In Activity Monitor's Memory tab, a red or yellow Memory Pressure graph means the Mac is short of memory, which makes apps hang more often. Quit apps you are not using.
- Wait instead of force quitting. If an app is briefly busy rather than truly stuck, giving it a moment avoids a force quit and the report that follows.
When should you worry about spindump?
spindump running for more than a few seconds at a time, or every few minutes, means apps keep hanging. Look at the spin reports for a common app or a system component.
Running sudo spindump by hand is safe but loads the Mac for its duration; do it only when you need a report.
How do you check spindump in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type spindump 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 spindump 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 'spindump' | grep -v grep
sudo fs_usage -w -f filesys spindump
How can Thrum help with spindump?
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 spindump 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 spindump
Can I disable spindump?
There is no user setting for it, and it only runs when there is something to report. Fixing the app that hangs is the real fix.
Where are spindump reports?
In /Library/Logs/DiagnosticReports/. Console shows them under Spin Reports; you need an administrator account to see system reports.
Sources
- spindump(8) man page: run man spindump in Terminal
- Apple Support: Run system diagnostics in Activity Monitor on Mac
- Apple Support: Reports in Console on Mac