Closed
Description
Setup
- Which version of Git for Windows are you using? Is it 32-bit or 64-bit?
64 bit
$ git --version --build-options
git version 2.36.0.windows.1
cpu: x86_64
built from commit: ea1e13f73339d57cbe81a0bae6fba669aaccf656
sizeof-long: 4
sizeof-size_t: 8
shell-path: /bin/sh
feature: fsmonitor--daemon
- Which version of Windows are you running? Vista, 7, 8, 10? Is it 32-bit or 64-bit?
Windows 10, 64 bit. 21H1
$ cmd.exe /c ver
Microsoft Windows [Version 10.0.19043.1645]
- What options did you set as part of the installation? Or did you choose the
defaults?
# One of the following:
> type "C:\Program Files\Git\etc\install-options.txt"
> type "C:\Program Files (x86)\Git\etc\install-options.txt"
> type "%USERPROFILE%\AppData\Local\Programs\Git\etc\install-options.txt"
$ cat /etc/install-options.txt
Editor Option: VIM
Custom Editor Path:
Default Branch Option:
Path Option: Cmd
SSH Option: OpenSSH
Tortoise Option: false
CURL Option: OpenSSL
CRLF Option: CRLFCommitAsIs
Bash Terminal Option: MinTTY
Git Pull Behavior Option: Merge
Use Credential Manager: Enabled
Performance Tweaks FSCache: Enabled
Enable Symlinks: Disabled
Enable Pseudo Console Support: Disabled
Enable FSMonitor: Disabled
- Any other interesting things about your environment that might be related
to the issue you're seeing?
nope
Details
- Which terminal/shell are you running Git from? e.g Bash/CMD/PowerShell/other
git bash
- What commands did you run to trigger this issue? If you can provide a
Minimal, Complete, and Verifiable example
this will help us understand the issue.
git init
dd if=/dev/zero of=8gb bs=1024 count=$((1024*1024*8))
git lfs track 8gb
git add .
git commit
time git status
time git status
time git status
- What did you expect to occur after running these commands?
I expected the time to be less than one second.
- What actually happened instead?
git commit and all the git status commands take over one minute.
Files that are larger or smaller than 8GB seem to work as expected.
@bk2204 says this is not related to LFS. See 4983.
- If the problem was occurring with a specific repository, can you provide the
URL to that repository to help us with testing?
N/A