Understanding Core Symbolication
In macOS, when an application crashes, the operating system generates a detailed crash report (a `.crash` or `.spin` file) that developers can use to diagnose the failure. To make these logs readable by humans, macOS uses a background framework called Core Symbolication (CoreSymbolication.framework) to translate raw hexadecimal memory addresses into actual function names and lines of code (a process called “symbolicating”).
Because symbolicating is highly CPU-intensive, macOS aggressively caches the results in a hidden system directory. However, if this cache becomes corrupted, the entire Core Symbolication framework can freeze. Symptoms of this include the Console app crashing immediately upon launch, the Activity Monitor failing to load process names, or the ReportCrash daemon consuming 100% of the CPU in the background while attempting to process a log.
To resolve this, you must forcefully purge the Core Symbolication cache using the Terminal.
Locating the Cache Directory
The Core Symbolication cache is not located in the standard user ~/Library/Caches folder. It is deeply buried in the secure, root-level temporary directories managed by the Darwin kernel.
Specifically, the cache files reside in the /System/Library/Caches/com.apple.coresymbolicationd directory.
Clearing the Cache via Terminal
Because this directory is owned by the root user and protected by System Integrity Protection (SIP) layer permissions, you cannot simply drag it to the Trash in Finder. You must use the terminal with administrator privileges.
- Open the Terminal application.
- Execute the following command to forcefully remove the entire contents of the cache directory:
sudo rm -rf /System/Library/Caches/com.apple.coresymbolicationd/*Press Enter, type your Mac’s administrator password (it will remain hidden), and press Enter again.
Warning: The rm -rf command is incredibly destructive if typed incorrectly. Ensure you have typed the exact path before pressing Enter.
Restarting the Daemon
Just deleting the files is not enough, because the background daemon responsible for symbolication (coresymbolicationd) is actively running in memory and still clinging to the old, corrupted data pointers.
You must forcefully kill the daemon, allowing macOS’s launchd system to instantly respawn a fresh, clean instance of it.
sudo killall coresymbolicationdThe Final Step
For the absolute best results, it is highly recommended to reboot the Mac immediately after executing these two commands. Upon restart, the fresh coresymbolicationd process will generate a brand new, uncorrupted cache architecture. The Activity Monitor will regain its responsiveness, and the Console app will successfully parse crash logs without locking up the CPU.