Hi folks, I came across a Windows user today whose "fetch" operations were taking a long time, because their repository had passed some persistent maintenance-triggering threshold *and* the resulting auto-gc was running in the foreground (and not resolving the maintenance-triggering condition automatically). The user was seeing, at the end of their fetch, something like: Auto packing the repository in background for optimum performance. See "git help gc" for manual housekeeping. Enumerating objects: 311322, done. Nothing new to pack. Checking connectivity: 1490123 Eventually, they noticed a subsequent recommendation to run "git prune", after the connectivity check completed, and after they did the git prune, they started getting "bad object" errors on fetch - so there was clearly something else going wrong somewhere... But my *question* is: Does anyone know where I could/should look to understand why the GC was happening in the foreground, even though the message says it will run in the background? I don't know how to create the conditions for the auto-GC on demand (how to create lots of loose objects??), so I don't know how to verify whether it ever runs in the background on Windows, or what that might depend on. I saw some discussions in 2016, but I can't tell what the conclusion was; is it simply the case that git has been "lying" about running GC in the background, on windows, for all these years? Or is there something specific going on in this user's environment? Any info welcome, thank you! Tao
