Orphaned git.exe processes pile up

“In a large repository a new one is started every few seconds, so these orphaned git.exe processes pile up until the machine runs out of memory.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/claude-code/issues/636/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Quiet. No reports and thumbs-up in the last two weeks, down from 3 a week at the late-September peak.

Orphaned git.exe processes accumulate on Windows. Claude Code's git calls leave the real git.exe running after the Git for Windows launcher is killed or its parent exits.

Is this your bug?

File my report

Where: git integration
Versions: 2.1.267 to 2.1.296
Platforms: Windows

Part of: Killed commands leave orphaned processes5 bugs

Orphaned processes after task stop8 people
Hook timeout hangs tool call2 people
Worktree isolation refused2 people
Stopping background Bash task leaves child process running, output file grows2 people

Not quite your bug?

claude.exe pins one CPU core after watched directory is deleted5 people
Desktop memory and process buildup2 people

Original reports4, newest first

Oct 11, 2026claude agents --json leaves suspended git ... remote children behind (Windows)#101182
Sep 30, 2026[Windows][WSL] Desktop diff-panel git probes still leak orphaned git.exe after #94655, when the session's folder is in WSL (\\wsl.localhost)#98440
Sep 28, 2026Windows: timed-out git status leaves orphaned git.exe processes that pile up until memory is exhausted#97752
Sep 15, 2026[Windows] Desktop git-shadow probes leak orphaned git.exe on large SMB repos — timeout kills the Git for Windows launcher, not git; 55 procs / 20 GB in 1 h (follow-up to #86646)#94655