Runtime Error. git.exe R6016 - not enough space for thread data

[Lebreux]

I get this error when doing merge, rebase, checkout, almost anything really. This error does not appear consistently.

Windows 7 Enterprise 64-bit

[andrecastelo]

I have the same problem. Upon machine restart, the problem goes away and Git Bash is very fast. A few minutes later, it's unusable, incredibly laggy and taking a long time to do anything.

Windows 7 64bit as well, with Git for Windows 1.9.5

[linquize]

Large repo? Lots of files in a commit? Long history? How large is it?

[andrecastelo]

I'm getting this on varied projects with different sources. Some from github and some from bitbucket, and none more than 13 months old.

The Git bash itself is incredibly slow, and I found no way to "reset" it other than restarting Windows.

[Lebreux]

Our repository has 6614 files in it. The biggest file we have controlled is 4.04Mb. Repository is brand new, migrating from VSS without keeping history.

[t-b]

@ShadowXV5 Is this repository, or one which shows the bug, available to the public? My largest repository is >20GB with tens of thousands of files, I've never saw this bug on Win7 Pro x64. Including files up to a hundred MB.

[Lebreux]

Unfortunately, this repository is not available to the public. However, I am able to reproduce the same error using a brand new empty repository. Edit: This can also be reproduced on another Win7x64 computer.

[julio-bittencourt]

Hi, I have exactly the same problem with my windows 7 Professional SP1 64 bits. Any advice on a solution would be very appreciated. Thanks.

[SoboLAN]

I use msysGit 1.9.2 (not 1.9.5) on 3 different Windows 7 machines with repositories ranging from just a few hundred kilobytes up to and including repositories as large as 3GB containing 100.000 files.

In this configuration, I never ever saw the error you mention.

I recommend downgrading back to v1.9.2 as a workaround.

[dscho]

I recommend downgrading back to v1.9.2 as a workaround.

And of course you add the caveat emptor that this re-introduces a rather big security bug.

The most likely future solution is to switch to the upcoming 64-bit version of Git for Windows, where these address range problems should not be an issue any longer.

[SoboLAN]

@dscho What security bug are you referring to ?

[kusma]

@SoboLAN: CVE-2014-9390

[saulovenancio]

I have the same probelm here. That is the third windows installation that has this problem. And there is not documentaiton on how to solve it. Any help?

[dscho]

@saulovenancio please try out the latest release candidate of Git for Windows 2.x.

[dscho]

@saulovenancio you might also want to install the 64-bit version instead of the 32-bit version; That should make it much more unlikely for the bug to re-appear. However, if it does, please open a new ticket with Git for Windows 2.x (because that version retired Git for Windows 1.x).