Hi Johannes, I am not sure the Fast Track release means. Do you refer to Windows 10 builds (updates)? I am running Windows 7 x64 and haven't gone to Windows 10. Default memory allocation in Windows is bottom-up, which means the lowest addresses are consumed the first. This is all fine until the address is over 4GB on x64 OS with more than 4GB physical memories. Many applications don't handle it properly and will crash. Windows provides a registry key to force OS allocating memory from the highest address available first and going down the chain as a way to test application's memory management. That's what I did on my host to test our own software. And it affected Git 2.7.0.2 (latest build for Windows from 2/2/2016). I had to rollback to Git 1.8.4 to work around this problem. 1.8.4 is a 32-bit build not 64-bit build. That's why it worked so far. Thanks Xia -----Original Message----- From: Johannes Schindelin [mailto:Johannes.Schindelin@xxxxxx] Sent: Thursday, February 04, 2016 2:46 AM To: Klinger, Xia Cc: git@xxxxxxxxxxxxxxx Subject: Re: git 2.7.0 crashes when top-down memory allocation preference is set Hi, On Wed, 3 Feb 2016, Klinger, Xia wrote: > When the memory allocation preference is set to be Top-down on Windows > and there are more than 4GB memory available, git will crash. The > symptom is "Segmentation Fault". This might be related to https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_git-2Dfor-2Dwindows_git_issues_627&d=CwIBAg&c=VCWpAYkS3z1bOCIxc-BPGZarCq9MRCAVxZJE051VqH8&r=67DEVp3lXDRlQoHC5xXHqK4qsTItx9yvwX98R_Hn9tg&m=jBFYZYDLdCLg-WMJPpbvl9rXn4syBv9RAGsbi106m3Y&s=MaQ04pu8kp8pdAOjVSd1PCqEwsYMpxpsFiqZ100gkrk&e= Do you have access to the Fast Track releases? If so, Windows 10 build 14257 was released to it and purportedly fixes these issues. Ciao, Johannes -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html