Thrum

What is XCBBuildService, and why is it using so much CPU or memory?

Last reviewed: 19 November 2026. Path, bundle ID and bundle contents checked with Xcode 26.6 on macOS 26.3.1.

XCBBuildService is the Xcode build system: it reads your project, works out what needs rebuilding, and starts the compilers, linkers and other tools that do the work. It is busy while you build, and it stays alive between builds holding the build graph in memory. Most of the CPU during a build is in the swift-frontend and clang processes it starts, not in XCBBuildService itself.

XCBBuildService at a glance

XCBBuildService
Made byApple (part of Xcode)
TypeBuild service (Xcode build system)
Location/Applications/Xcode.app/Contents/SharedFrameworks/XCBuild.framework/Versions/A/PlugIns/XCBBuildService.bundle/Contents/MacOS/XCBBuildService
Runs asyour user
Bundle IDcom.apple.dt.XCBBuildService
Can you quit it?Yes, but a build in progress fails. Xcode starts a new build service for the next build.

What is XCBBuildService?

Xcode keeps the build system in a separate service process. Apple has open-sourced Swift Build, which its README describes as a high-level build system based on llbuild that is used by Swift Package Manager, Xcode and Swift Playground. Xcode 26.6 contains both XCBBuildService.bundle and Swift Build's SWBBuildService.bundle, so depending on the Xcode version Activity Monitor may show either name.

During a build, the service starts many child processes: swift-frontend for Swift, clang for C and Objective-C, ibtool for storyboards, the linker, and code signing. Its own CPU covers planning the build, checking which files changed, and collecting results.

Is XCBBuildService safe?

Yes. It lives inside Xcode's shared frameworks, is signed by Apple, and only runs while Xcode or xcodebuild uses it.

Why does XCBBuildService use so much CPU, memory and disk?

How much CPU is normal for XCBBuildService?

Activity during builds and near 0% CPU between them is the normal pattern. Its memory often stays raised after a build while Xcode is open.

Most of the CPU in a build appears under swift-frontend and clang processes.

How do you make Xcode builds use less CPU?

  1. See where build time goes. Run xcodebuild -showBuildTimingSummary with your usual scheme to print the time spent in each kind of command.
  2. Limit parallel jobs. xcodebuild -jobs 2 sets the maximum number of concurrent build operations, which keeps a command-line build from using every core.
  3. Fix scripts that always run. In each Run Script phase, declare input and output files so Xcode can skip the script when nothing changed.
  4. Clean when the build graph is confused. Choose Product > Clean Build Folder (Shift-Command-K) if builds rebuild everything every time or fail for no reason, then build again.

When should you worry about XCBBuildService?

High CPU from XCBBuildService with no build running, or memory that keeps growing across builds, can be cleared by quitting and reopening Xcode.

A process with this name outside Xcode.app is not Apple's.

How do you check XCBBuildService in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), and type XCBBuildService in the search field. The CPU tab shows its % CPU. The Memory tab shows its Memory. The Disk tab shows its Bytes Written and Bytes Read. Double-click the row for its parent process, memory details and open files.

In Terminal, the first command lists every XCBBuildService process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). fs_usage prints each file it reads or writes until you press Control-C; it needs an administrator password.

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'XCBBuildService' | grep -v grep
sudo fs_usage -w -f filesys XCBBuildService

How can Thrum help with XCBBuildService?

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 XCBBuildService 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. Click XCBBuildService in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.

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 XCBBuildService

Can I quit XCBBuildService?

Yes, when no build is running. Xcode starts it again when you build. Quitting it during a build makes that build fail.

Where does XCBBuildService write files?

Into the project's folder in DerivedData, by default ~/Library/Developer/Xcode/DerivedData. Deleting a project's folder there forces a full rebuild.

Sources