On 2023-05-16 at 17:54:41, Tim Walter (Visual Concepts) wrote:
> Windows 10 PC
> large project
> 300GB
> 500,000 files
> mix of binary and text assets.
> 
> cd /d D:\myproject
> git init --separate-git-dir=F:\myproject.git
> git add *
> 
> Git runs for a little while then hangs and does some really bad things to the OS as well.
> it seems impossible to kill git.exe even with administrator priviledges.
> f: drive ends up locked and any other process, such as explorer that try to look at it also hang
> you cannot log out without hanging
> or even restart
> This then requires a hard power cycle to fix.
>
> 100% reproducable.
> 
> running git init without --separate-git-dir and git add * works fine (takes 3 hours,.. but works)
> then I can move the .git dir to f: and reinit with --separate-git-dir and that works.
> So this seems to only be a problem for the initial init.

I don't use Windows so I can't verify this, but I would not expect this
problem to occur.  Even hashing 500,000 files consuming 300 GB should
not hang the computer or take 3 hours.

What kind of disk is F:?  Is it an external disk (USB or such, and if
so, what speed and kind)?  Is it a network drive?  Is it another local
disk in the computer (SSD or HDD)?

Are you using an antivirus or firewall other than the default, or any
sort of other monitoring software?  What I suspect is happening here is
that you have an antivirus intercepting Git's operations and scanning
the files for viruses, making everything really slow, and then at some
point a bug occurs in the antivirus (which may have a kernel driver) and
then things hang.  This is probably made worse if F: is an external
drive or network drive.

If you are, can you try to completely uninstall that software and
reboot, and then try again?
-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA