maintenance stuck forever in commit-graph

[kkmuffme]

Existing issues matching what you're seeing

• I was not able to find an open or closed issue matching what I'm seeing

Git for Windows version

git version 2.51.0.windows.1
cpu: x86_64
built from commit: 4d21a77b98af5cf479d8b6f863c2aa94257cd4e1
sizeof-long: 4
sizeof-size_t: 8
shell-path: D:/git-sdk-64-build-installers/usr/bin/sh
feature: fsmonitor--daemon
libcurl: 8.15.0
OpenSSL: OpenSSL 3.2.4 11 Feb 2025
zlib: 1.3.1
SHA-1: SHA1_DC
SHA-256: SHA256_BLK
default-ref-format: files
default-hash: sha1

Windows version

Windows 11

Windows CPU architecture

x86_64 (64-bit)

Additional Windows version information

Options set during installation

Editor Option: VIM
Custom Editor Path:
Default Branch Option:
Path Option: Cmd
SSH Option: ExternalOpenSSH
Tortoise Option: false
CURL Option: OpenSSL
CRLF Option: CRLFCommitAsIs
Bash Terminal Option: MinTTY
Git Pull Behavior Option: FFOnly
Use Credential Manager: Enabled
Performance Tweaks FSCache: Enabled
Enable Symlinks: Disabled
Enable FSMonitor: Disabled

However these are only the install, I currently have Symlinks and FSMonitor enabled and working

Other interesting things

I posted this here, since the same repo under linux does not seem to have this problem.
I have the same repo cloned (and maintenance enabled) multiple times on the device, and the same issue happens in all of them

Terminal/shell

bash

Commands that trigger the issue

git config maintenance.commit-graph.schedule hourly
git config gc.autoDetach false
git config maintenance.autoDetach false
git config maintenance.gc.enabled false
git config gc.writeCommitGraph false
# next lines are probably irrelevant, just here for completeness
git config maintenance.prefetch.schedule hourly
git config maintenance.loose-objects.schedule hourly
git config maintenance.incremental-repack.schedule hourly
git maintenance start

Expected behaviour

maintenance and commit-graph should run and finish

Actual behaviour

maintenance is started automatically, I see

git -C C:/path/to/repo maintenance run --schedule=hourly

However, it gets stuck (= blocked/doing nothing) at:

git commit-graph write --split --reachable --progress

with 0 CPU time forever
Additionally, because the .git\objects\maintenance.lock is created, no maintenance will happen at all and it's stuck forever (actually it will crash/restart computer at some point, which means that maintenance doesn't run at all bc maintenance.lock still exists)

Deleting that lock file and manually running the commit-graph command in the repo works perfectly fine and finishes too.

Repository

No response

[dscho]

Could you please install Git for Windows' SDK, then build Git (via sdk build git in the Git SDK Bash), then run the mentioned command using the just-built git.exe (/usr/src/git/bin-wrappers/git commit-graph write --split --reachable --progress), then attach in gdb in a second Git SDK Bash (gdb /usr/src/git/git.exe <pid> where <pid> is the process ID as per, say, ProcMon)?

If that works, you should be able to press Ctrl+C in the gdb session to pause the process and look around (info threads is interesting, as you will be on the debug thread started via Ctrl+C, and thread 1 followed by bt will typically show you the most informative thread stack trace).

[kkmuffme]

It does not run bc of the maintenance.lock file afaik, I deleted it and then it ran fine - until when at some point this happens again after some days/weeks.
I guess there should be some logic that if the maintenance.lock file is not actually locked or older than x days it should just ignore it?

I had this issue in multiple repos, in 1 case it turned out that there was some pack file corruption or something, bc when I manually ran it I got

warning: failed to add packfile '.git/objects/pack/pack-ff6afb73451605de48dccefb691a10cde0e664f1.idx'

However, unfortunately the output of the scheduled maintenance ends up in the abyss on windows or is it written to a log file somewhere, which makes these things go unnoticed?