WhySlow
What is logd on Mac?
Collects log messages from every app and service.
Why is logd using so much CPU?
Busy when an app writes huge amounts of log messages, often during a bug or crash loop.
Should you quit logd?
No. logd is part of macOS. Quitting it can break things, and macOS starts it again anyway. When it is busy, it usually calms down once its work is done.
Is logd a virus?
No. logd is a genuine part of macOS, signed by Apple and stored in a protected system folder that apps can't change. Malware sometimes borrows familiar names, so if a process called logd lives outside /System or /usr, or you see it after installing something unusual, run a check with a trusted tool and keep macOS up to date.
How to check logd on your Mac
Open Activity Monitor (Applications › Utilities), choose the CPU tab and type logd in the search field. The % CPU column shows how busy it is: 100% means one full processor core. The Memory tab shows how much memory it uses. Activity Monitor shows numbers but doesn't say what they mean; WhySlow explains logd in plain English and only flags it when it is really slowing your Mac down.
What to do if logd stays busy
- Wait 10 to 15 minutes. Most macOS background work finishes on its own.
- If logd stays busy for more than a day, restart your Mac. That clears a stuck process safely.
- Keep macOS up to date: Apple fixes runaway background processes in updates.
How WhySlow helps with logd
- Shows how much CPU and memory logd is using right now, in plain English.
- Tells you when logd is the real cause of a slow Mac, and when it isn't.
Free to explain. $7 once for one-click fixes.