Cloning/Pulling with Git LFS on Windows creates excessive temporary files

[Richard Copperwaite]

We use SourceTree on several machines, and we've noticed all of them have started losing lots of disk space, tens of GB in some cases, to hundreds of 'bbchunkdl' files (e.g. 'bbchunkdl214143915' or similar) in the <User>\AppData\Local\Temp directory.

We have not been able to trace the file creation handles to a specific process, but we've noticed that their creation times seem to correlate with SourceTree Pull/Clone operations, and we've seen them created in the directory at the moment of a SourceTree Pull. 

All of our repositories use Git LFS, and with LFS being such a new and actively-developed feature, and the naming convention seeming to fit (bbchunkdl - binary blob chunk download?) it seemed reasonable to assume that LFS might be the culprit. 

These files don't seem to be used after a Pull/Clone, so they seem to be safe to delete. Is anybody else seeing this issue?

[Matthew Hodges]

3 years on - I'm getting exactly this too with LFS.  I routinely have to clear out the bbchunkdl* files from AppData\Local\Temp.