What is coresymbolicationd, and why is it using CPU on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
coresymbolicationd manages the system cache of symbol information for macOS libraries: the data that turns raw memory addresses in crash reports, hang reports and samples into function names. It is busy when such reports are created or when debugging and profiling tools run. It is part of macOS and settles on its own.
coresymbolicationd at a glance
| coresymbolicationd | |
|---|---|
| Made by | Apple (part of macOS, CoreSymbolication) |
| Type | System daemon |
| Location | /System/Library/PrivateFrameworks/CoreSymbolication.framework/coresymbolicationd |
| Runs as | root |
| Started by | launchd job com.apple.coresymbolicationd |
| Can you quit it? | Yes, but launchd starts it again when symbols are needed. |
What is coresymbolicationd?
The man page says coresymbolicationd "manages the system cache of symbol information for OS libraries. Users can directly view or modify the contents of this cache using the symbolscache(1) utility." Symbolication is the step that converts addresses such as 0x7fff8d662779 into readable names like __CFRunLoopRun, as the spindump man page shows.
It lives inside the CoreSymbolication framework and runs as root from the com.apple.coresymbolicationd launchd job. Crash reporting, spindump, sample, Activity Monitor's Sample Process and developer tools all need symbols.
Is coresymbolicationd safe?
Yes. It is part of macOS in a framework on the read-only system volume. It only manages symbol data; it does not change any program.
Why does coresymbolicationd use so much CPU and disk?
- Reports and samples being symbolicated. Every crash report, spin report or process sample needs symbol lookups, so a burst of crashes or hangs means a burst of work.
- Debuggers and profilers. Xcode, Instruments and command-line tools such as
sampleandspindumpsymbolicate many addresses at once. - Updating its cache. Adding entries to the symbols cache writes to disk.
How much CPU is normal for coresymbolicationd?
Usually idle or not running. Bursts during crash reporting, sampling or right after a macOS update are normal.
How do you stop coresymbolicationd from using so much CPU?
- Check for crash or hang loops. Open Console and look at Crash Reports and Spin Reports. A program that crashes or hangs repeatedly keeps symbolication busy.
- Stop profiling sessions. If Instruments, a debugger or a sampling script is running, stopping it stops the symbol lookups.
- Restart if it never settles. If it stays busy with no reports or tools running, restart the Mac to start it fresh.
When should you worry about coresymbolicationd?
coresymbolicationd busy for hours with no crashes, hangs or developer tools in use is unusual; a restart is the first step.
Do not delete or edit the symbols cache with symbolscache unless you know you need to; it is rebuilt as needed but rebuilding costs CPU.
How do you check coresymbolicationd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type coresymbolicationd in the search field. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every coresymbolicationd 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 'coresymbolicationd' | grep -v grep
sudo fs_usage -w -f filesys <PID> # PID from the ps line above
How can Thrum help with coresymbolicationd?
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 coresymbolicationd 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 coresymbolicationd
What is symbolication?
Turning the memory addresses recorded in a crash report or sample into the names of the functions that were running, so the report can be read.
Does coresymbolicationd send data anywhere?
Its man page describes only managing a local cache of symbol information. Sending reports is handled by other processes and follows your analytics settings.
Sources
- coresymbolicationd(8) and symbolscache(1) man pages: run man coresymbolicationd in Terminal
- spindump(8) man page: run man spindump in Terminal