The process cannot access the file because it is being used by another process – TortoiseGit status cache under concurrent requests

Goal: Determine the exact concurrency threshold at which TortoiseGit's shared status cache begins to exhibit file‑system lock contention that triggers Windows error 32.

Constraints: Working copy larger than 10 000 files, status cache set to the default (shell) mode, real‑time antivirus scanning the .git directory, and simultaneous launch of TortoiseGit context menus, commit dialogs, or log views.

Uncertainty: Whether adjusting the cache refresh interval, limiting parallel overlay requests, or excluding specific file patterns can reduce lock duration without disabling icon overlays.

Questions: What is the maximum number of simultaneous TortoiseGit UI operations that can be performed before lock contention appears? Does reducing the status cache refresh interval lower the probability of error 32 while preserving overlay accuracy? Can excluding the .git/index file from antivirus real‑time scanning eliminate the latency without disabling the status cache?