Why is git using CPU or disk on my Mac when I am not running it?
Last reviewed: 19 November 2026. /usr/bin/git and its Xcode target (Apple Git-155, Git 2.50.1) checked on macOS 26.3.1.
git processes come from more than your own commands: editors and Git apps run git status and git fetch to keep their views current, git gc --auto tidies a repository in the background, scheduled maintenance can run every hour, and the fsmonitor daemon watches a working folder. Large repositories make all of these heavier. The command line of the process tells you which one you are seeing.
git at a glance
| git | |
|---|---|
| Made by | The Git project; Apple ships a build with Xcode and the Command Line Tools |
| Type | Version control command |
| Location | /usr/bin/git |
| Runs as | your user |
| Can you quit it? | Yes, but an interrupted fetch, clone or garbage collection may need to be run again. |
What is git?
/usr/bin/git runs the Git from the active Xcode or Command Line Tools folder (xcrun --find git shows it), and Homebrew installs its own in /opt/homebrew/bin. Many programs call git: Xcode's source control, Visual Studio Code (which uses the Git installed on your machine), Git clients, shell prompts that show the current branch, and build tools.
Git also has its own background work. Commands that create objects check whether the repository has grown and then run git gc --auto, which by default detaches and runs in the background. git maintenance start registers launchd jobs in ~/Library/LaunchAgents (org.git-scm.git.hourly, .daily and .weekly). With core.fsmonitor set to true, a built-in git fsmonitor--daemon stays running to watch a working folder.
Is git safe?
Yes. Git from Xcode or the Command Line Tools is signed by Apple, and the processes only work on repositories on your Mac. Their command lines name the repository folder and the git subcommand.
Why does git use so much CPU, disk, network and memory?
- Editors refreshing status. Editors and Git apps run
git statusand similar commands whenever files change, and in a large repository each run has to check many files. - Automatic garbage collection.
git gc --autopacks loose objects once there are about 6,700 of them (thegc.autodefault) or more than 50 packs, rewriting pack files on disk. - Background fetch and prefetch. Editors that fetch periodically, and the hourly prefetch task of
git maintenance, download objects from remotes in the background. - Clones, checkouts and rebases. Large clones decompress and check out many files, and rebasing or switching branches in big repositories rewrites many files at once.
- The fsmonitor daemon. The built-in fsmonitor daemon stays running for each working folder it watches, so commands like
git statuscan ask it for changes instead of scanning the disk.
How much CPU is normal for git?
Short-lived git processes that appear and exit within a second are normal, especially while an editor is open on a repository.
Longer runs with high CPU and disk activity happen during clones, fetches of large histories and garbage collection, and end when the command completes.
How do you find which git process is busy and calm it down?
- Read its command line. Run
ps -axo pid,ppid,args | grep [g]it. The subcommand (status,fetch,gc,maintenance,fsmonitor--daemon) and the parent PID show what is running and who started it. - Check for scheduled maintenance. Look for
org.git-scm.git.*.plistin~/Library/LaunchAgents.git maintenance stopremoves the schedule;git maintenance unregistertakes only the current repository off the list. - Stop an fsmonitor daemon. In the repository, run
git fsmonitor--daemon statusto see whether one is watching it, andgit fsmonitor--daemon stopto stop it. Settingcore.fsmonitorto false keeps it from starting again. - Let garbage collection finish once. If
git gcis running, let it complete; later runs then have little to do. Runninggit gcyourself at a convenient time has the same effect. - Reduce editor polling. Close editor windows on large repositories you are not working in, and turn off automatic fetching in your Git client if you do not need it.
When should you worry about git?
Repeated git processes using CPU with no editor or Git app open point to a launchd job or script; check ~/Library/LaunchAgents and the parent PID.
If git gc --auto runs on every command, the repository may keep exceeding the limits; running a full git gc once usually stops that.
How do you check git in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type git in the search field. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. The Network tab shows its Sent Bytes and Rcvd Bytes. The Memory tab shows its Memory. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every git 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. nettop shows its live network traffic.
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'git' | grep -v grep
sudo fs_usage -w -f filesys git
nettop -p git
How can Thrum help with git?
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 git 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 git 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 git
Why does git run when I open a folder in my editor?
Editors run git to show the current branch, changed files and line changes. Visual Studio Code, for example, uses the Git installed on your Mac for its source control features.
Is /usr/bin/git the same as Xcode's git?
Yes. /usr/bin/git runs the Git from the developer folder chosen with xcode-select, which on the Mac used for checking was Apple Git-155 (Git 2.50.1).