The Dock, the app at the bottom of the screen
The bar at the bottom of your screen is a full app: a four-line manual page, twelve system doors, helper processes and its own database. Measured: 9.6 MB, a minute and a half of CPU a day, one silent restart.
By Chethan Kumar S N · Updated
You have rearranged this one more than anything else on your Mac. The bar at the bottom of the screen is the first thing people customise and the last thing they think about: it holds your apps, your Downloads, your Trash, the windows you minimise, the row of desktops when you swipe up. All of that is one app, the app is a process, and the process has a manual page that is four lines long and ends in a joke.
This page is a measurement of the Dock on a Mac running macOS 27.0.1 with 29 days 22 hours of uptime, 10 cores, 32 GB of memory. Every fact below was read off the system. Nothing was installed, nothing was killed, no setting was written.
The manual page is real, four lines, and ends in a joke
The series starts at the manual, and this time there is one. Unlike Finder, which has no manual entry at all, the Dock answers from the shell:
$ man Dock
Dock(8) System Manager's Manual Dock(8)
NAME
Dock - Provides the Dock interface for the system
DESCRIPTION
Dock dock goose
There are no options for Dock, and users should not
run Dock manually.
macOS July 4, 2018 Dock(8)
“Dock dock goose.” An Apple engineer typed a duck-duck-goose pun into the system manual, dated it July 4, 2018, and it shipped. The same file also lives inside the app bundle at /System/Library/CoreServices/Dock.app/Contents/Resources/Dock.8, in case the manual index ever loses it. The useful line is the last one: users should not run Dock manually. Everything on this page is about reading it, not running it.
A birth certificate identical to Finder’s
The Dock is not a daemon either. Its launch file sits in /System/Library/LaunchAgents, the user-level folder, and reads like the Finder’s with one letter changed:
Label => com.apple.Dock.agent
Program => /System/Library/CoreServices/Dock.app/...
POSIXSpawnType => App
RunAtLoad => false
KeepAlive => { AfterInitialDemand => true,
SuccessfulExit => false }
ThrottleInterval => 1
launchd’s live report fills in the behaviour, and one number in it tells a story the Finder guide could only hint at:
state = running
runs = 2
pid = 86909
minimum runtime = 1
exit timeout = 5
immediate reason = semaphore
last exit code = 1
runs = 2. On a session that is 29 days 22 hours old, the Dock’s elapsed time is 26 days 12 hours: the bar restarted, once, silently, about three and a half days into this session, and has been on its second life ever since. The Finder page caught the same event from the other side, a sibling ps sweep where the file manager’s report still read runs = 1, never exited. The taskbar blinked out and back one night and nobody logged a complaint.
A small naming trap worth knowing: the running service is com.apple.Dock.agent, because com.apple.Dock plain is not a registered label in your session. The same discipline that keeps Finder killable keeps the Dock killable: KeepAlive with SuccessfulExit = false means launchd brings it back whenever it goes away, and ThrottleInterval = 1 means it skips the usual cool-down.
The bar is also a switchboard
The launch file has one more section, and it is the answer to what the Dock actually does all day. Twelve MachServices doors, every one of them marked HideUntilCheckIn:
com.apple.dock.appstore
com.apple.dock.downloads
com.apple.dock.fullscreen
com.apple.dock.launchpad
com.apple.dock.notificationcenter
com.apple.dock.ppt
com.apple.dock.remotedesktoppicture
com.apple.dock.server
com.apple.dock.sidecar
com.apple.dock.spaces
com.apple.dock.spotlight
com.apple.desktoppicture.cache-delete
Each door is another part of the system checking in with the bar. Full screen transitions. Spaces, which is why the thumbnail row appears inside the Dock when you swipe. The Notification Center reveal. Launchpad, whose door is still in the file even on a Mac where the feature itself has been folded into the app library. The App Store’s install progress, the Downloads stack, Sidecar, Spotlight’s screen position.
The picture that comes out of the plist is that the Dock is not a decoration at the bottom of the screen, it is a piece of furniture the whole system leans on. launchd’s report says active count = 12 at the moment of reading: twelve of those doors held a live client. The bar you see is the visible tenth of it.
dock extra and dock helper, decoded
Search for the Dock and the autocomplete offers two odd rows: dock extra and dock helper. Both decode cleanly on a stock Mac.
Dock extra is a field in the Dock’s own database. Every icon entry in it, all three app tiles and the Downloads folder on this machine, carries a dock-extra key, reading 0 for ordinary tiles. The name also belongs to real processes: inside Dock.app sit three XPC services, com.apple.dock.external.extra in both arm64 and x86-64 flavours plus com.apple.dock.extra, small binaries of about 207 KB. One was alive on the measured Mac: six and a half days up, 5 MB of memory, 2.46 seconds of total processor time. The helpers come and go. The bar stays.
Dock helper is a different service, DockHelper.xpc, and it signs its work. Its binary holds the build string PROJECT:Dock-2571.0.6.402, which is as close to a version number as the Dock ever shows you, plus a small cast of classes with plain jobs: MenuHelper for the menus it draws, TransparentWindow for click-through regions, AccessibilityOverride. Nothing here is third party, nothing is watching you, and none of it should be quit by hand. When the bar needs help it checks in, and when it does not the helpers are not running.
One more job hides in this same process: the window view. The Dock binary holds the whole Expose engine and ships the 24 images of the Spaces bar, which is why the app called Mission Control in your Applications folder is only a 133 KB bell and why no process with that name exists in Activity Monitor. The Mission Control page takes that machinery apart.
Its own little database
The Dock keeps its state in your home folder, and you can read it the same way it does:
$ defaults read com.apple.dock
autohide = 0
orientation = bottom
tilesize = 31
trash-full = 1
mod-count = 751
mod-count is the quiet headline. 751 modifications to the bar on this Mac: icons added, removed, dragged, reordered, every one counted since the account was born. There is probably no other object on your machine you have reconfigured 751 times.
The rest of the file is the bar itself as data. Three app tiles, each a record with a GUID, a bundle identifier, a label, a file type, and that dock-extra = 0 flag. One folder tile, Downloads, of tile-type directory-tile. trash-full = 1 is the flag that puts the little paper ball into the Trash icon, which is the Dock rendering a Finder fact. tilesize = 31 is 31 pixels of icon, a stock setting nobody has touched on this machine, and orientation = bottom says the bar never moved either. The most rearranged object on the Mac, and half its settings are still factory.
Even the menus are files
Control-click an icon in the bar and a menu appears. Apple documents that menu in one line, “Control-click an item to display its shortcut menu, then choose an action, such as Show Recents”. What the doc does not say is that the menu is defined as data, sitting in the app bundle as DockMenus.plist. The folder tile’s menu, verbatim from the file:
SORT_BY
NAME
DATE_ADDED
DATE_MODIFIED
DATE_CREATED
KIND
Sort by name, date added, date modified, date created, kind: the five folder views in the Dock’s stacks, listed as numbered commands, 3001 through 3006, with a separator at 2000. The strings file beside it holds the rest of the vocabulary, including the row every stack eventually shows, “More in Finder”, with a counter in front of it. The bar’s whole personality is on disk, in plists, readable.
What Apple documents, and what it never says
The user guide has a page called Use the Dock, and it is a good one. It opens with a definition, “The Dock on the Mac desktop is a convenient place to access apps and features you’re likely to use every day”, and carries facts worth keeping: the bar “can show up to three recently used apps that aren’t already in it”, the separator line can be dragged to resize it, Fn-Control-F3 moves keyboard focus into the bar and the arrow keys walk icon to icon. On removing an icon: “Only the alias is removed; the actual item remains on your Mac.” That one sentence answers the add and remove questions the autocomplete keeps asking, because adding an item to the Dock puts an alias there, not the thing itself.
What the page never says, anywhere in its body, is the word process. Zero mentions. Apple documents the Dock the way a car manual documents the boot: as a place. The pid, the restart, the twelve doors, the 751 modifications, the goose joke, all of that lives below the water line, which is where this series does its measuring.
The bill
Two readings, minutes apart:
| Reading | Value |
|---|---|
| Memory (RSS) | 16,048 KB, then 15,424 KB |
| Virtual size | 489,291,296 KB, about 466 GB |
| Processor time | 39 minutes 50 seconds across 26d 12h |
| Per day | about a minute and a half, 0.1 percent of one core |
| CPU right now | 0.0 percent |
| Runs | 2, one silent restart, second life 26 days old |
A minute and a half a day is the honest price of the bar: the magnification, the previews, the Spaces row, the Trash icon knowing it is full. When the column climbs well past that, the work is almost always real and visible, and the reset is the second oldest safe remedy on the Mac:
killall Dock
The bar blinks out and returns in about a second, windows untouched, wallpaper and menu bar belonging to other processes entirely. If it climbs straight back, the culprit is usually one icon: a stack pointing at a folder that changes thousands of times a minute, a cloud sync client updating its badge, an app rewriting its own icon. Kill the bar and it comes back clean. Then watch the neighbours, not the bar.
Questions
What is the Dock on my Mac?
It is an app, the same kind of thing as Safari or Notes, except it never quits and you launch everything else from it. On the measured Mac it is pid 86909, started by launchd as com.apple.Dock.agent, running as your own account out of /System/Library/CoreServices/Dock.app with a 9.6 MB binary. Apple's user guide describes it as a convenient place to access apps and features you are likely to use every day, which covers the bar itself, the Trash, the Downloads stack, the row of desktop thumbnails when you use Spaces, and the area where minimised windows wait. Its preferences are a database in your home folder, and on this Mac it records 751 modifications since the account was set up, which makes it probably the most reconfigured object on the machine.
What is dock extra or dock helper on my Mac?
Two different things that both show up in searches. Dock extra is a per-tile flag inside the Dock's own database: every icon entry carries a dock-extra field, reading 0 for ordinary tiles. The name also belongs to real helper processes: the Dock app ships three extra services in its XPCServices folder, com.apple.dock.external.extra for arm64 and x86-64 plus com.apple.dock.extra, and one of them was alive on the measured Mac with 5 MB of memory and under three seconds of processor time across six days. Dock helper is a separate 335 KB service named DockHelper whose own build string reads PROJECT:Dock-2571.0.6.402, holding menu and transparent window classes. None of these are malware and none should be quit by hand; they start when the bar needs them and go away when it does not.
Why is the Dock using so much memory or CPU?
The honest floor is low. The process held 16 MB of real memory in the first reading and 15 MB in the second, minutes apart, with a falling number, which is the healthy pattern. The column that alarms people is virtual memory, about 466 GB, which is address space the process reserved, not RAM it is holding, the same pattern Finder, loginwindow and audiomxd showed earlier in this series. Processor time was 39 minutes 50 seconds across 26 and a half days, about a minute and a half a day, a tenth of one percent of a single core. When it climbs past that, the causes are visible work: magnification during fast pointer sweeps, live folder and stacks previews, wallpaper transitions during full screen switches, and the Spaces thumbnail row. A Dock stuck at high CPU with the pointer parked usually means one icon is misbehaving, and the reset below is safe.
Is it safe to killall Dock?
Yes, it is one of the oldest safe remedies on the Mac, and unlike loginwindow, where killall logs you out, the launch file is built for restarts. It sets KeepAlive with SuccessfulExit = false and ThrottleInterval = 1, so launchd brings the bar back immediately, and launchd's live report shows a minimum runtime of one second. This Mac is the proof by accident: the report reads runs = 2, last exit code = 1, and the elapsed time says the current copy has been up 26 and a half days on a 29 day session. The Dock already restarted itself once, silently, three and a half days in, and the only reason anyone noticed is that ps keeps count. Your windows stay open, the wallpaper and menu bar belong to other processes, and the bar blinks out and back in about a second.
Can the Dock be a virus or malware?
The genuine process runs from /System/Library/CoreServices/Dock.app on the sealed read-only system volume, signed by Apple as part of the OS and built only for Apple silicon, arm64e, on this machine. A process named Dock running from a downloads folder or a temp folder would be a costume, and the check is the same as for every process in this series: open Activity Monitor, select the process, click the info button and read the full path. There is no known malware family that impersonates this name. One honest confusion to avoid: the Dock and Docker are unrelated, and the autocomplete for killall dock offers killall docker right below it. Quitting Docker containers and restarting the bar are different chores.
Ready? Buy Ribbon for $15, or read all the guides.