Thrum

What is diagnosticd, 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.

diagnosticd is the part of the macOS unified logging system that serves live log data to viewers such as the Console app and the log stream command. It uses CPU only while something is watching logs live, and Apple's man page notes that this costs extra system resources. Closing Console or stopping log stream brings it back to idle.

diagnosticd at a glance

diagnosticd
Made byApple (part of macOS, unified logging)
TypeSystem daemon
Location/usr/libexec/diagnosticd
Runs asroot
Started bylaunchd job com.apple.diagnosticd
Can you quit it?Yes, but live log viewers stop receiving data until it restarts.

What is diagnosticd?

The man page says diagnosticd "is part of the unified logging system. It helps serve live debugging information. For example, it manages and delivers data to Console.app and the log(1) utility's stream command." Messages are written by apps through os_log, stored by logd, and, while someone is streaming, copied out by diagnosticd.

The same man page warns that "when Console.app or log stream are actively displaying ongoing system data, diagnosticd and os_log(3) calls require extra system resources (e.g., CPU) to serve this data live." It runs as root from the com.apple.diagnosticd launchd job.

Is diagnosticd safe?

Yes. It is part of macOS in /usr/libexec on the read-only system volume. High CPU from it almost always has a simple cause: a live log view is open.

Why does diagnosticd use so much CPU?

How much CPU is normal for diagnosticd?

Idle or not running when nothing is viewing logs live. Raised CPU while Console or log stream is open is expected and stops when they stop.

How do you stop diagnosticd from using so much CPU?

  1. Stop streaming in Console. In Console, click the Pause or Stop button for the live log view, or quit Console.
  2. Stop log stream. Find any Terminal window running log stream and press Control-C.
  3. Filter instead of streaming everything. When you need live logs, filter to one process, for example log stream --process Safari, so less data is delivered.
  4. Check for tools that stream logs. If neither Console nor Terminal is streaming, quit developer tools or monitoring apps one at a time to see which one is reading logs.

When should you worry about diagnosticd?

diagnosticd at high CPU with no log viewer open is unusual. Look for a background tool that streams logs.

A diagnosticd running from outside /usr/libexec would not be Apple's.

How do you check diagnosticd in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type diagnosticd in the search field. The CPU tab shows its % CPU. Double-click the row for its parent process, memory details and open files.

In Terminal, the first command lists every diagnosticd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'diagnosticd' | grep -v grep

How can Thrum help with diagnosticd?

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 diagnosticd 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 diagnosticd

Does diagnosticd store logs?

No. Storing logs is logd's job. diagnosticd delivers live data to viewers while they are open.

Why does opening Console slow down my Mac?

Apple's man page explains that live display makes diagnosticd and the logging calls of every app use extra resources. Pausing the stream removes that cost.

Sources