fatal: the remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed

Question

Error produced in Sourcetree...

git -c filter.lfs.smudge= -c filter.lfs.required=false -c diff.mnemonicprefix=false -c core.quotepath=false --no-optional-locks clone --branch master https://Gary.Herber@bitbucketdev.gdit.com/scm/gdit/gditdba_repo.git C:\bit9prog\dev\gditdba_repo
Cloning into 'C:\bit9prog\dev\gditdba_repo'...
error: RPC failed; curl 18 transfer closed with outstanding read data remaining
fatal: the remote end hung up unexpectedly

fatal: early EOF
fatal: index-pack failed
Completed with errors, see above.

So far nothing has worked, other repos on this server can be cloned...

GSHerber · Answer

Here is the answer that was developed. First the repo was large; on the order of 4gb and that was too much for git in the default configuration. So first reduced the size of the repo by getting all the redundant CIs removed and removing the the 3rd party software packages that the team was 'storing' in Bitbucket. Then have the team switch from https to ssh. Ssh seems to be able to handle the larger chunks of data better than https. We also set 'git config --global core.compression=0', this helped some wasn't enough by itself.