# Activity Monitor, the app that watches everything else

> The app in your Utilities folder: version 10.14 on a Mac running macOS 27, seven tabs, 31 sortable columns, an eleven signal menu and a helper for diagnostics. Measured on a real Mac.

Source: https://www.ribbonmac.com/guides/activity-monitor-mac · Updated 2026-11-19

Something is wrong with the Mac. Fans, heat, a beachball, a battery draining by lunch. You open the app everyone tells you to open, a table of every running process fills the screen, and now you are looking at a hundred rows with names like bird and trustd and kernel_task, a second table of numbers at the bottom, and no introduction anywhere.

This page is the introduction, and it is also a measurement of the app itself. The Mac used here runs macOS 27.0.1 with 10 cores and 32 GB of memory. Every fact below was read off the system or from Apple's own thirteen article user guide for this one app. Nothing was installed, nothing was quit, no setting was written.

## The app with a version number from another decade

Start with its birth certificate, read from the bundle:

```
Path       /System/Applications/Utilities/Activity Monitor.app
Binary     1,382,304 bytes
Archs      arm64e, arm64e.x1
Identifier com.apple.ActivityMonitor
Version    10.14 (build 1040)
Minimum    macOS 27.0
```

Version 10.14, on a Mac whose system calls itself 27. The app keeps its own version line and has for years, which is why the About box never matches the OS. It is signed like the rest of the system, it sits on the sealed read-only volume, and it loads 26 libraries to do its work.

That library list is the honest feature list. CoreSymbolication is there, the symbolication engine that powers the Sample Process button. libIOReport, the framework behind the Energy tab. NetworkStatistics for the network tab, AssetCacheServicesExtensions for the Cache tab, SafeEjectGPU for GPU handling, CrashReporterSupport for hang detection. And one library this series has met before: libsysmon, the client end of the sysmond daemon. The app you use to watch processes does not read the kernel's tables itself. It asks a clerk, and the clerk's page is [sysmond, the daemon that fills in the numbers](https://www.ribbonmac.com/guides/sysmond-mac).

## Seven tabs, and the second one is newer than you think

The tab bar on macOS 27 reads, left to right, out of the app's own interface strings:

```
CPU   GPU   Memory   Energy   Disk   Network   Cache
```

Two of those are surprises. GPU sits second, between CPU and Memory, with columns of its own, % GPU and GPU Time, and a summary strip that reports the graphics card by name, its utilisation, and the maximum bandwidth of the connection to the GPU. Apple's GPU article frames the whole tab in one sentence: "If you see many tall blue bars packed tightly together, consider using an external GPU to handle some of the workload."

Cache is the other surprise, because on most Macs it does not exist. The tab only appears when Content Caching is switched on in System Settings, General, Sharing, and Apple's article says so plainly: if you cannot see the Cache tab, turn on Content Caching, then quit and reopen Activity Monitor. It is the only tab that hides, and it is the only one with no process list at all, just data served, dropped and fetched from parents and peers, a ledger for a machine that caches updates for other devices.

The CPU tab is the classic, and the five default columns on a stock Mac are Process Name, % CPU, CPU Time, Threads and PID, sorted by % CPU with the heaviest at top. Energy tracks Power Score and 12 hr Power, and on laptops it is the tab that names names: which apps prevent sleep, which nap, which demand the high performance GPU.

## Thirty one columns, and one of the menus is a Unix manual

Open View > Columns and the list runs past two screens: 31 sortable columns besides the name, from Threads and Idle Wake Ups to Purgeable Memory, Sandbox, Restricted and Sudden Termination. The widths of all 31 are stored per tab, in the app's own preferences domain, which is how this was counted.

But the deeper cut of the app's personality is View > Send Signal to Process. The menu it opens is a Unix signals course, verbatim from the app's strings:

```
Hangup (SIGHUP)            Interrupt (SIGINT)
Quit (SIGQUIT)             Abort (SIGABRT)
Kill (SIGKILL)             Alarm (SIGALRM)
Stop (SIGSTOP)             Continue (SIGCONT)
User Defined 1 (SIGUSR1)   User Defined 2 (SIGUSR2)
Information Request (SIGINFO)
```

Eleven signals, the same ones a shell user can send with kill, sitting two menu levels below a table most people use like Task Manager. SIGINFO is the charming one: it asks a process to print its status, the Ctrl-T of the [terminal](https://www.ribbonmac.com/guides/terminal-mac) world, available here by mouse.

## What the X button actually does

Select a process, click the X in the corner, and the app offers two buttons with precise meanings. Apple's own words for them:

Quit: "This is the same as choosing File > Quit within an app. The process quits when it's safe to do so. If quitting the process could cause data loss or interfere with another app, the process doesn't quit."

Force Quit: "The process quits immediately. If the process has files open, you may lose data. If the process is used by other apps or processes, those apps or processes could experience problems."

That second sentence is the one worth memorising, because the table does not show dependency. Apple's own follow up tip: to see if a process is used by another process, choose View > All Processes, Hierarchically, and children appear under their parents. An unresponsive process is marked (Not Responding) and shows red before you ever click anything.

If you quit a process you do not own, the app "may require you to authenticate as an administrator", and that is where its companion comes in.

## The diagnostic kit under the gear

The gear menu holds four tools most people never open, and Apple's book defines each in one line. Sample Process: "Creates a report on a selected process over a period of 3 seconds." Spindump: "Creates a report for unresponsive apps that were terminated using force quit." System Diagnostics: "Creates a report based on different logs on your Mac." Spotlight Diagnostics: "Creates a report based on all the processes running on your Mac."

Three seconds is the honest surprise. The Sampler in this app watches a process for three seconds, stacks every call it makes, and hands you the profile, which is most of what the big profiling tools give you for the first three seconds anyway.

Those buttons are also why the app ships a helper. Inside the bundle sits com.apple.activitymonitor.helper.xpc, 204,000 bytes, version 10.12, linked against libsysdiagnose and SecurityFoundation. It is the privilege lane: diagnostics need rights the app itself does not hold, the helper asks you for the administrator password, and the app's own strings describe the finish line: "When the diagnostic is complete, a Finder window displays the results." Searches that ask about Activity Monitor Helper using high CPU are usually seeing this helper mid report. It runs for the length of the collection and stops.

## The number that goes over 100

The question the autocomplete asks most often about this app is what the % CPU column means when it passes 100. Measured, not explained. Four saturating processes were started on this 10 core Mac and read together after five seconds:

```
PID     %CPU  COMMAND
50005   96.9  yes
50006   96.3  yes
50007   97.2  yes
50008   95.9  yes
```

Roughly 390 percent in one screenshot, on a machine that still had 60 percent of its capacity idle. The column prices a single core at 100. A process with work spread across many threads reads several hundred the moment it uses them. And the numbers at the bottom of the window are the other scale entirely, Apple defines them as percentages of total CPU capability: System, "used by processes that belong to macOS", User, "used by apps you opened, or by the processes opened by those apps", and Idle, "not being used". Those three aim at 100 together. Both scales are correct. They just measure different things.

The same section of the window answers the memory questions. The Memory tab's footer holds the Memory Pressure graph, and Apple's colour code is worth trusting: green means the Mac "is using all its RAM efficiently", yellow means it "might eventually need more RAM", red means "your computer needs more RAM". Wired, Compressed and Cached Files each get a one line definition in the book, and there is even an article titled Check if your Mac needs more RAM, which ends at Option > Apple menu > System Information > Memory, where an Upgradeable Memory row tells you whether more RAM is a purchase or an impossibility. On Apple silicon it is almost always the second.

## The app that remembers you

Activity Monitor was not running on the measured Mac, but its preferences file remembered the last visit, and the contents are a small portrait of how anyone actually uses this app:

```
SelectedTab = 0                (the CPU tab)
NSWindow Frame = 1139 x 1017   on a 1728 x 1084 screen
UpdateFrequency                (absent, so the default holds)
```

The absent key is the telling one. The app's update menu offers Very often (1 sec), Often (2 sec) and Normally (5 sec), and on this Mac the setting was never changed from Normally, because almost nobody opens that menu. The default costs almost nothing. Turn it to 1 second and the app starts polling for fresh rows every second, and as the [sysmond page](https://www.ribbonmac.com/guides/sysmond-mac) measures, the two processes whose CPU columns move first are Activity Monitor itself and the daemon answering it. Apple documents the experiment, and the warning, in the help book: watch the CPU Time column as you change the frequency.

Two smaller tools complete the kit. View > Dock Icon turns the Dock icon itself into a live graph, Show CPU Usage or Show CPU History, a tiny dashboard most people have never seen. And the Filter Process box in the corner does what a hundred row table always needed: type three letters and the table becomes one process. The search field, Apple notes, is also the fastest way to answer "what is this name", because it filters as you type.

## See for yourself

Every fact above came from read only commands:

```
ls -l /System/Applications/Utilities/Activity\ Monitor.app/Contents/MacOS/
codesign -dv /System/Applications/Utilities/Activity\ Monitor.app
otool -L /System/Applications/Utilities/Activity\ Monitor.app/Contents/MacOS/Activity\ Monitor
plutil -p /System/Applications/Utilities/Activity\ Monitor.app/Contents/Resources/Defaults.plist
defaults read com.apple.ActivityMonitor
```

The defaults line is the one that repays the reading: window frame, chosen tab, column widths, all 31 of them, a complete record of how you last left the table. And the next time a row in that table worries you, kernel_task, WindowServer, bird, the odds are good this series has already measured it. Start with [kernel_task](https://www.ribbonmac.com/guides/what-is-kernel-task-on-mac) and [WindowServer](https://www.ribbonmac.com/guides/what-is-windowserver-on-mac), the two rows everyone stares at first, and if the Mac is slow rather than scary, the [ledger of quiet processes](https://www.ribbonmac.com/guides/why-is-my-mac-running-slow) prices them one by one.

## FAQ

### What is Activity Monitor on my Mac?

It is an app, the same class of thing as Safari or Notes, that lives in your Utilities folder and lists every process on the machine with live numbers for each. Apple's own user guide, a thirteen article book dedicated to this one app, defines the subject in its first line: Processes are programs running on your Mac. Processes can be apps, system apps used by macOS or invisible background processes. On the Mac measured here it is a 1,382,304 byte binary at /System/Applications/Utilities/Activity Monitor.app, version 10.14 build 1040, an app that keeps its own version line while the operating system around it moved to 27. It has seven tabs, thirty one sortable columns besides the name, and it is the front end of a daemon. Every number in its table is fetched for it by sysmond, a process this series has measured separately.

### Why does the CPU column show over 100 percent?

Because the column prices one core at 100, not the whole machine. Measured live on a 10 core Mac: four saturating processes read 96.9, 96.3, 97.2 and 95.9 percent at the same moment, roughly 390 percent total, while 60 percent of the machine sat idle. A single process that spreads work across many cores, a video encoder, or kernel_task during Spotlight indexing, reads several hundred percent for the same reason. The percentages at the bottom of the window are the other scale: Apple defines System as the percentage of CPU capability being used by processes that belong to macOS, User as the percentage used by apps you opened, and Idle as the percentage not being used, and those three always add to about 100.

### What should I quit in Activity Monitor, and is Force Quit safe?

Quit things you opened, and read before you shoot. The X button offers two options and Apple defines both. Quit is the same as choosing File > Quit within an app. The process quits when it is safe to do so. If quitting the process could cause data loss or interfere with another app, the process does not quit. Force Quit quits immediately, and if the process has files open, you may lose data. An unresponsive process is marked (Not Responding) and appears red. Processes you do not own may ask you to authenticate as an administrator, and system processes like kernel_task, WindowServer and sysmond should be left alone; the first two have their own pages in this series. Before force quitting anything you do not recognise, choose View > All Processes, Hierarchically, Apple's own tip, to see whether other processes depend on it.

### What is Activity Monitor Helper, and is it malware?

It is a real component, not malware. Inside the app bundle sits an XPC service, com.apple.activitymonitor.helper.xpc, a 204,000 byte binary reporting version 10.12, and its two interesting library links tell its whole job: libsysdiagnose, the system that collects diagnostic reports, and SecurityFoundation, the authentication layer. It exists because the diagnostic options under the gear button, Spindump, System Diagnostics and Spotlight Diagnostics, need privileges the app itself does not hold. It wakes when you run a diagnostic and goes away again. The usual costume test applies to any process: the real one runs from inside the app bundle on the sealed system volume, and a process with a similar name running from a downloads folder would be a fake.

### Why do processes show root and _windowserver as their user?

Because every process on a Mac runs as an account, and there are more accounts on the machine than the one you log in with. root owns the system's own machinery, launchd, kernel_task, most of the daemons in this series. _windowserver is a service account for the process that draws everything on screen; underscores in front of a name are the convention for these service accounts, like _spotlight or _locationd. The User column and the View menu let you slice them: My Processes shows only what your account owns, Other Users' Processes shows the rest. None of these accounts is a person and none is a sign of anything wrong. It is the same account separation the whole Unix world has used for decades, visible because this app lists everything.
