If Activity Monitor shows codesign using a large amount of CPU, do not delete the process or disable macOS security. Code signing is part of Apple’s security system: macOS uses signatures to verify an app’s identity and detect whether its code has been changed.
Confirm what is happening
- Open Applications > Utilities > Activity Monitor.
- Select the CPU tab and sort by % CPU.
- Observe the Mac for several minutes. Short bursts can occur while an app is being installed, updated, opened, or checked.
- Note which app was opened or updated immediately before the high usage began.
Safe troubleshooting steps
1. Restart the Mac
A normal restart clears temporary processes and is the safest first step. After signing in, allow startup activity to settle before checking Activity Monitor again.
2. Update macOS and your apps
Open System Settings > General > Software Update and install compatible macOS updates. Update third-party apps through the App Store or the developer’s official update system. An incomplete or repeatedly failing app update can cause verification work to recur.
3. Review recent software
If the issue began after installing or updating one app, quit that app and check whether CPU usage returns to normal. Remove an app only with its official uninstaller or the developer’s documented method. Avoid deleting unknown files from system folders.
4. Test in Safe Mode
Safe Mode can help determine whether software that loads at startup is contributing to the problem. Apple silicon and Intel Macs use different startup procedures, so follow Apple’s instructions for your model. If the problem disappears in Safe Mode, restart normally and review recent login items, extensions, security tools, and background apps.
5. Review login items
Open System Settings > General > Login Items & Extensions. Temporarily turn off a recently added nonessential background item, restart, and test again. Change one item at a time so you can identify the cause.
What not to do
- Do not delete code-signing components.
- Do not disable Gatekeeper or bypass signature checks to reduce CPU use.
- Do not run unverified Terminal commands copied from random forums.
- Do not force-quit unrelated system processes repeatedly.
When to contact Apple
Contact Apple Support if codesign remains at high CPU for long periods after a restart, updates, and a Safe Mode test, or if the Mac repeatedly overheats or becomes unusable. Record the Mac model, macOS version, the affected app, and a screenshot of Activity Monitor. That information can help support identify whether the behavior is tied to macOS or a particular application.
Comments
Post a Comment