Git for windows crashed in Windows 10 latest build (14251.1000) #627

likidu · 2016-01-28T06:47:50Z

Hi,

I got Git crash immediately running under latest insider build of 14251.1000. I knew its arguable about the "latest" one, but please help. Thank you.

Git for Windows version 2.7.0.

lashchev · 2016-01-28T06:55:18Z

Same problem here :-(

alexsh · 2016-01-28T08:10:12Z

Same problem here, error module is ntdll.dll, exception code: 0xc0000005

dscho · 2016-01-28T08:26:57Z

People. Please read our issue reporting guidelines and improve this report accordingly. Anything else will only result in major frustration on all sides, and that is not what anybody would possibly want.

paladox · 2016-01-28T11:23:51Z

I also get this problem when using git command. It crashes git. I also get Segmentation fault inside the git program.

dscho · 2016-01-28T11:44:42Z

@paladox and you also do not list precise version informations as well as a precise account (preferably with a copy-paste of the output) of what you did. Really, please read the issue reporting guide lines. It is really frustrating to receive so incomplete information.

paladox · 2016-01-28T11:47:16Z

Sorry. When running git --version I get Segmentation fault because of git command being faulty in the latest windows 10 insider build as of 27/01/2016. Also I am running 2.7.0 64-bit.

paladox · 2016-01-28T11:48:12Z

@dscho All I do is start git bash from the windows start button then in git bash I do this command git to test it. And returns Segmentation fault.

dscho · 2016-01-28T11:49:43Z

Did you try cmd, what commands crash, etc etc etc etc etc

paladox · 2016-01-28T11:52:36Z

yes. As soon as I enter git in cmd running as admin it brings up the crash dialog for git for windows.

Also when starting git ui I get this error popup

cannot determine git version:

child kild: segmentation violation

git gui requires git 1.5.0 or later.

dscho · 2016-01-28T12:01:18Z

What happens when you run net use /? in cmd?

paladox · 2016-01-28T12:48:34Z

When I run net use /? it brings up the Net Command has stopped working.

Briles · 2016-01-28T16:00:03Z

I'm having the same issue in Windows 10 14251.1000 64-bit and 64-bit Git versions later than 2.6.2.windows.1

Running installed or portable git.exe results in Git for Windows has stopped working error message and logs the following in Event Viewer:

Faulting application name: git.exe, version: 2.7.0.0, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.14251.1000, time stamp: 0x56a54488
Exception code: 0xc0000005
Fault offset: 0x00000000000a6eeb
Faulting process id: 0xc50
Faulting application start time: 0x01d159deab2de7c2
Faulting application path: C:\PortableGit-2.7.0-64-bit\mingw64\bin\git.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 31967d76-6b7d-4e9f-af3b-40ae2867739c
Faulting package full name: 
Faulting package-relative application ID:

Running net use /? results in:

Faulting application name: net.exe, version: 10.0.14251.1000, time stamp: 0x56a54798
Faulting module name: ucrtbase.dll, version: 10.0.14251.1000, time stamp: 0x56a5447e
Exception code: 0xc0000005
Fault offset: 0x0000000000021415
Faulting process id: 0xf58
Faulting application start time: 0x01d159dbc6b316a7
Faulting application path: C:\WINDOWS\system32\net.exe
Faulting module path: C:\WINDOWS\system32\ucrtbase.dll
Report Id: 89cf4fbc-8269-41c7-8595-970945bda050
Faulting package full name: 
Faulting package-relative application ID:

Git-gui also fails to start with:

Cannot determine Git version:
child killed: segmentation violation
Git Gui requires Git 1.5.0 or later.

Running git from Bash results in:


Brian@Brian-PC MINGW64 /
$ git --version
Segmentation fault

jaccarmac · 2016-01-28T17:28:46Z

Running git from CMD results in a "Git for Windows has stopped working" message. Running the command from Git Bash results in a segmentation fault.

Windows 10 rs1_release 14251, Git, 2.7.0.0.

Log Name:      Application
Source:        Application Error
Date:          28-Jan-16 10:24:27
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      valentine
Description:
Faulting application name: git.exe, version: 2.7.0.0, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.14251.1000, time stamp: 0x56a54488
Exception code: 0xc0000005
Fault offset: 0x00000000000a6eeb
Faulting process id: 0x1188
Faulting application start time: 0x01d159f0bd604efe
Faulting application path: C:\Program Files\Git\mingw64\bin\git.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 26293b56-fb4b-4f4f-a875-399a099f81de
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-01-28T17:24:27.501423400Z" />
    <EventRecordID>625</EventRecordID>
    <Channel>Application</Channel>
    <Computer>valentine</Computer>
    <Security />
  </System>
  <EventData>
    <Data>git.exe</Data>
    <Data>2.7.0.0</Data>
    <Data>00000000</Data>
    <Data>ntdll.dll</Data>
    <Data>10.0.14251.1000</Data>
    <Data>56a54488</Data>
    <Data>c0000005</Data>
    <Data>00000000000a6eeb</Data>
    <Data>1188</Data>
    <Data>01d159f0bd604efe</Data>
    <Data>C:\Program Files\Git\mingw64\bin\git.exe</Data>
    <Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
    <Data>26293b56-fb4b-4f4f-a875-399a099f81de</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

heldchen · 2016-01-28T18:15:05Z

same here: Windows 10 Pro Insider Preview x64 build 14251.rs1_release.160124-1059, Git x64, v2.7.0.0.

if the WER reports are of any use, I can provide them privately.

Log Name:      Application
Source:        Application Error
Date:          28.01.2016 18:58:48
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      X-WING
Description:
Faulting application name: git.exe, version: 2.7.0.0, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.14251.1000, time stamp: 0x56a54488
Exception code: 0xc0000005
Fault offset: 0x00000000000a6eeb
Faulting process id: 0x3188
Faulting application start time: 0x01d159f589ae1376
Faulting application path: C:\Program Files\Git\mingw64\bin\git.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 67e92489-a5fa-4010-9adf-8d04be5d0f31
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-01-28T17:58:48.285256200Z" />
    <EventRecordID>655</EventRecordID>
    <Channel>Application</Channel>
    <Computer>X-WING</Computer>
    <Security />
  </System>
  <EventData>
    <Data>git.exe</Data>
    <Data>2.7.0.0</Data>
    <Data>00000000</Data>
    <Data>ntdll.dll</Data>
    <Data>10.0.14251.1000</Data>
    <Data>56a54488</Data>
    <Data>c0000005</Data>
    <Data>00000000000a6eeb</Data>
    <Data>3188</Data>
    <Data>01d159f589ae1376</Data>
    <Data>C:\Program Files\Git\mingw64\bin\git.exe</Data>
    <Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
    <Data>67e92489-a5fa-4010-9adf-8d04be5d0f31</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Log Name:      Application
Source:        Windows Error Reporting
Date:          28.01.2016 18:58:50
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      X-WING
Description:
Fault bucket 120399744865, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: git.exe
P2: 2.7.0.0
P3: 00000000
P4: ntdll.dll
P5: 10.0.14251.1000
P6: 56a54488
P7: c0000005
P8: 00000000000a6eeb
P9: 
P10: 

Attached files:
C:\ProgramData\Microsoft\Windows\WER\Temp\WER4CE5.tmp.WERInternalMetadata.xml
C:\Users\Me\AppData\Local\Temp\WER54C6.tmp.appcompat.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_git.exe_d792d3b2e130c95f532e21b8c261b227ab646c8_da76d18a_36f75532

Analysis symbol: 
Rechecking for solution: 0
Report Id: 67e92489-a5fa-4010-9adf-8d04be5d0f31
Report Status: 1
Hashed bucket: 97b4e7a1d26115cd399602c67e2da1ff
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-01-28T17:58:50.532295500Z" />
    <EventRecordID>656</EventRecordID>
    <Channel>Application</Channel>
    <Computer>X-WING</Computer>
    <Security />
  </System>
  <EventData>
    <Data>120399744865</Data>
    <Data>4</Data>
    <Data>APPCRASH</Data>
    <Data>Not available</Data>
    <Data>0</Data>
    <Data>git.exe</Data>
    <Data>2.7.0.0</Data>
    <Data>00000000</Data>
    <Data>ntdll.dll</Data>
    <Data>10.0.14251.1000</Data>
    <Data>56a54488</Data>
    <Data>c0000005</Data>
    <Data>00000000000a6eeb</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
C:\ProgramData\Microsoft\Windows\WER\Temp\WER4CE5.tmp.WERInternalMetadata.xml
C:\Users\Me\AppData\Local\Temp\WER54C6.tmp.appcompat.txt</Data>
    <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_git.exe_d792d3b2e130c95f532e21b8c261b227ab646c8_da76d18a_36f75532</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>67e92489-a5fa-4010-9adf-8d04be5d0f31</Data>
    <Data>1</Data>
    <Data>97b4e7a1d26115cd399602c67e2da1ff</Data>
  </EventData>
</Event>

kowsheek · 2016-01-28T19:35:41Z

Same issue here

Log Name:      Application
Source:        Application Error
Date:          1/28/16 2:33:34 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      KATRA
Description:
Faulting application name: git.exe, version: 2.7.0.0, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.14251.1000, time stamp: 0x56a54488
Exception code: 0xc0000005
Fault offset: 0x00000000000a6eeb
Faulting process id: 0x1da4
Faulting application start time: 0x01d15a02c7130628
Faulting application path: C:\Program Files\Git\mingw64\bin\git.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: cf21ce19-c83a-46d1-9a44-3dba8a9e6971
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-01-28T19:33:34.754836400Z" />
    <EventRecordID>1363</EventRecordID>
    <Channel>Application</Channel>
    <Computer>KATRA</Computer>
    <Security />
  </System>
  <EventData>
    <Data>git.exe</Data>
    <Data>2.7.0.0</Data>
    <Data>00000000</Data>
    <Data>ntdll.dll</Data>
    <Data>10.0.14251.1000</Data>
    <Data>56a54488</Data>
    <Data>c0000005</Data>
    <Data>00000000000a6eeb</Data>
    <Data>1da4</Data>
    <Data>01d15a02c7130628</Data>
    <Data>C:\Program Files\Git\mingw64\bin\git.exe</Data>
    <Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
    <Data>cf21ce19-c83a-46d1-9a44-3dba8a9e6971</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

sailro · 2016-01-28T20:00:42Z

Same issue here, but probably due to this Windows build in my opinion (Windows 10 Pro Insider Preview x64 build 14251.rs1_release.160124-1059). Git 2.7.0 x32 or x64 is completely broken, unable to run Git (the installer is also failing when trying to call git). Git 2.6.2 works locally, but I cannot pull or push (git-remote-https was unable to start correctly error code 0x0000142).

net use /? is also crashing on my machine.
Unhandled exception at 0x00007FFADBED1415 (ucrtbase.dll) in net.exe: 0xC0000005: Access violation writing location 0x00000000000019D0.

Looking at this windows build changelog:
Known issues:
•Due to a recent memory management change, you may see periodic app crashes or other memory related app errors. The workaround is to reboot your PC.

...

kowsheek · 2016-01-28T20:36:06Z

@sailro I restarted several times (before reinstall and after) no luck.

I installed git version 1.9.4.msysgit.0 and it seems to be working with push and no crashes as yet.

shiftkey · 2016-01-28T20:40:55Z

It was brought to my attention by @onovotny that you should be able to workaround this issue by installing an earlier version of Git for Windows:

For those people running into git crashes on Windows 10 14521, install 2.6.1 (it'll downgrade higher vers): https://github.com/git-for-windows/git/releases/tag/v2.6.1.windows.1
https://twitter.com/onovotny/status/692538905539780609

clairernovotny · 2016-01-28T20:44:43Z

Seems like 2.6.2 also works.

sailro · 2016-01-28T20:45:58Z

@onovotny 2.6.2 works locally but crash with network actions (pull/push). I will try 2.6.1 then 1.9.x

sailro · 2016-01-28T20:50:43Z

@onovotny 2.6.1 crash also with network actions (pull/push)

clairernovotny · 2016-01-28T20:51:34Z

awesome! isn't it great to be on beta OS code :)

FWIW, there is a note in the release notes that things may crash in this build due to changes in the memory manager. I would expect this to be fixed in the next build or two; I doubt there's really any need to fix anything in Git.

sailro · 2016-01-28T20:52:39Z

I love that :(. After next release I will opt out

clairernovotny · 2016-01-28T20:53:33Z

So now the Q is what's the latest version that works? :)

sailro · 2016-01-28T20:54:47Z

https://github.com/msysgit/msysgit/releases/tag/Git-1.9.5-preview20150319 works

sailro · 2016-01-28T20:55:16Z

We have to rollback to the 1.9.x generation with msysgit

clairernovotny · 2016-01-28T21:00:55Z

Or us VS 2015 with LibGit2 to do network ops, at least until the next build ;)

How about a PowerShell script that wraps LibGit2 to do push/pull/fetch?

paladox · 2016-01-28T21:20:10Z

I rolled back to prevous build and now git works.

darrelmiller · 2016-01-28T22:28:47Z

Just as a point of reference, I'm running GFW 3.0.11.2 on Win10 14251.rs1_release.160124-1059 on a Surface Pro 3 and I am not seeing any issues.

bachagas · 2016-02-03T11:59:22Z

Hello there,

I confirm that this bug is fixed in Windows 10 build 14256.

I didn't get access to build 14256 yet, did anybody already have?

For those experiencing this issue and who really needs Git daily, a (maybe better) workaround than the suggested by Microsoft on the known issues (rollback to the previous build) is to use another git client that is independent of "Git for Windows", such as GitKraken .

Regards,

dscho · 2016-02-03T12:24:51Z

I didn't get access to build 14256 yet, did anybody already have?

Yes, I do ;-)

Seriously, you need to be prepared for things to break when you are on any kind of early access program. The entire point is to catch breakages early there. You will most likely find that Git for Windows is not the only application affected by the memory management issue, so eventually you will have to roll back anyway instead of keeping fire-fighting.

SeanBlader · 2016-02-03T16:22:39Z

Apologies to the interruption to dscho's day with this notification, but I just wanted to say thank you for the patch. I'm still on 14251 but as soon as I get access to 14256 I'll switch to the slow ring. If it makes you feel any better Microsoft also broke VirtualBox with this release. Those are the only two problems I've seen so far.

shiftkey · 2016-02-04T00:12:00Z

Build 14257 has just landed on the Fast Ring - https://twitter.com/GabeAul/status/695034380524216320

810 · 2016-02-04T01:44:17Z

For me Jenkins with git is now working, only there is still a issue with git desktop:

trace: built-in: git 'clone' '--progress' '--recursive' '--' 'https://github.com/810/Kunena-Forum.git' 'Kunena-Forum'
02:38:40.375513 run-command.c:335 trace: run_command: 'git-remote-https' 'origin' 'https://github.com/810/Kunena-Forum.git'
Cloning into 'Kunena-Forum'...
fatal: Unable to find remote helper for 'https'

So you can't send any PR

shiftkey · 2016-02-04T02:22:16Z

@810 can you confirm this is working with Git for Windows 2.7.x - I'm planning to update GitHub Desktop to this version very soon, and don't quite have access to the latest Fast Ring build...

810 · 2016-02-04T02:27:49Z

im running Git Desktop 3.0.12.0

But i have a response, from a microsoft edge program manager, and he said that the fix isn't in the new release. But he has to double check the issue now

shiftkey · 2016-02-04T02:29:42Z

@810 GitHub Desktop is using Git 2.5.3 for some operations - are you able to install Git for Windows 2.7.0 (can be installed alongside) and see that a clone succeeds?

810 · 2016-02-04T02:34:16Z

with 2.7.0 the same: fatal: Unable to find remote helper for 'https'

shiftkey · 2016-02-04T02:34:46Z

Ok cool, so we're not completely fixed yet. Thanks for confirming my suspicion.

shiftkey · 2016-02-04T04:41:57Z

@810 after discussing with more people as they've updated to 14257, I don't believe this is a general issue with the new release but something specific to your setup (as you could reproduce it across different versions of Git for Windows).

Please open a new issue with a Minimal, Complete, and Verifiable example to help us understand the issue you're seeing.

dscho · 2016-02-04T07:29:06Z

Apologies to the interruption to dscho's day with this notification

@SeanBlader apologies accepted. But please note that you are not interrupting my day. You are probably referring to my earlier unfortunate outbreaks when I was really struggling to get this bug fixed as soon as possible or at least to provide a work-around, and all I got for trying were remarks that seemed to be designed to make me feel bad for my efforts. I am certain you understand!

dscho · 2016-02-04T07:40:46Z

with 2.7.0 the same: fatal: Unable to find remote helper for 'https'

@810 @shiftkey this sounds like something deleted git-remote-https.exe. Or it could be there, but fails to find a dependency (maybe related to #390? But why would it still fail in 2.7.0, then?).

@810 can you look for the file C:\Program Files\Git\mingw64\libexec\git-core\git-remote-https.exe? (If you installed elsewhere, or the 32-bit version, please adjust the path accordingly.)

If it is not there, is it possible that some overzealous anti-virus in your setup quarantined it?

If it is there, could you open a Git Bash and try to run git remote-https bare-bones? It should output this:

$ git remote-https
error: remote-curl: usage: git remote-curl <remote> [<url>]

If it does not show that, could you use the Dependency Walker to see whether there are any DLL files that git-remote-https.exe depends on that are found in a strange place (you will want to switch on full paths with F9 or by right-clicking into the upper left panel)? For me, it shows this:

(sorry, I did not find a way to copy & paste this as text).

Another approach might be to look whether curl https://git-for-windows.github.io/ works as expected, or displays the same problems.

dscho · 2016-02-04T09:37:28Z

Update: I believe that this issue is related to top-down DLL loading. VirtualBox had similar issues: https://www.virtualbox.org/ticket/10128. When I set those registry entries accordingly, Git for Windows starts failing again, even with build 14257.

oysteinkrog · 2016-02-04T11:28:39Z

I can confirm that setting AllocationPreference as described causes mingw-w64-x86_64-git-2.7.0.2.57599f7-1 to crash with segmentation fault.
Windows 10 w/latest updates (not fast track).
Edit: gdb also segfaults

dscho · 2016-02-04T12:23:27Z

Hmm. According to the release notes of VirtualBox 4.2.2, issue 10128 was fixed with the note

NAT: fixed a crash under rare circumstances (Windows hosts only; bug ~~#10128~~)

But the commit with the message

Main/VirtualBox: fix crash in rare circumstances (only saw it with a severely corrupted inaccessible VM) on VM unregistration or on VBoxSVC termination

is particularly unhelpful: mirror/vbox@e1f2bde

So it sadly seems that we cannot imitate their fix.

810 · 2016-02-04T12:26:32Z

@810 can you look for the file C:\Program Files\Git\mingw64\libexec\git-core\git-remote-https.exe ? (If you installed elsewhere, or the 32-bit version, please adjust the path accordingly.)

C:\Users\jelle\AppData\Local\GitHub\PortableGit_c7e0cbde92ba565cb218a521411d0e854079a28c\mingw32\libexec\git-core File is there

If it is not there, is it possible that some overzealous anti-virus in your setup quarantined it?

Just windows defender

If it is there, could you open a Git Bash and try to run git remote-https bare-bones? It should output this

fatal: 'remote-https' appears to be a git command, but we were not able to execute it. Maybe git-remote-https is broken?

Another approach might be to look whether curl https://git-for-windows.github.io/ works as expected, or displays the same problems.

i see some html. so that worked.

I tried uninstalling git everywhere and installing again, same issue

dscho · 2016-02-04T12:42:03Z

@810 hmpf. It does not really look as if your problem matches the title of this ticket.

So let's avoid utter confusion and can I please have a new ticket for your issue?

dscho · 2016-02-05T09:31:07Z

Back to this ticket:

I can confirm that setting AllocationPreference as described causes mingw-w64-x86_64-git-2.7.0.2.57599f7-1 to crash with segmentation fault.
Windows 10 w/latest updates (not fast track).
Edit: gdb also segfaults

I found the culprit, and it has nothing to do with the reported crash in 14251. So let's stop here: a new Insider Preview has been released to the Fast Track, and Git for Windows works without any patch, so there was nothing Git for Windows had to fix.

oysteinkrog · 2016-02-05T19:29:19Z

dscho: That's awesome! Thanks for you hard work, this issue does not affect me, but I follow development of this project closely and I am very grateful for your efforts :)

dscho added the unclear label Jan 28, 2016

minarc mentioned this issue Feb 1, 2016

[surro] 윈도우에서 git bash를 쓸 때 segmentation fault 에러 D2CampusFest/3rd#29

Closed

This was referenced Feb 2, 2016

Segmentation Fault #641

Closed

Git 2.7.0 64bit becomes Segmentation fault on Windows 10 v10.0.14251 #642

Closed

Getting error using GUI #628

Closed

dscho mentioned this issue Feb 4, 2016

fatal: 'remote-https' appears to be a git command, but we were not able to execute it. Maybe git-remote-https is broken? #646

Closed

dscho removed bug unclear labels Feb 5, 2016

divmain mentioned this issue Feb 26, 2016

Trying to git status, getting git.exe stash list error timbrel/GitSavvy#360

Closed

dscho mentioned this issue Mar 2, 2016

git now crashes with access violation when run on particular machine #678

Closed

1 task

michael-vostrikov mentioned this issue Apr 21, 2016

Git for Windows crashes at start #741

Closed

1 task

Git for windows crashed in Windows 10 latest build (14251.1000) #627

Git for windows crashed in Windows 10 latest build (14251.1000) #627

Comments

likidu commented Jan 28, 2016

lashchev commented Jan 28, 2016

alexsh commented Jan 28, 2016

dscho commented Jan 28, 2016

paladox commented Jan 28, 2016

dscho commented Jan 28, 2016

paladox commented Jan 28, 2016

paladox commented Jan 28, 2016

dscho commented Jan 28, 2016

paladox commented Jan 28, 2016

dscho commented Jan 28, 2016

paladox commented Jan 28, 2016

Briles commented Jan 28, 2016

jaccarmac commented Jan 28, 2016

heldchen commented Jan 28, 2016

kowsheek commented Jan 28, 2016

sailro commented Jan 28, 2016

kowsheek commented Jan 28, 2016

shiftkey commented Jan 28, 2016

clairernovotny commented Jan 28, 2016

sailro commented Jan 28, 2016

sailro commented Jan 28, 2016

clairernovotny commented Jan 28, 2016

sailro commented Jan 28, 2016

clairernovotny commented Jan 28, 2016

sailro commented Jan 28, 2016

sailro commented Jan 28, 2016

clairernovotny commented Jan 28, 2016

paladox commented Jan 28, 2016

darrelmiller commented Jan 28, 2016

bachagas commented Feb 3, 2016

dscho commented Feb 3, 2016

SeanBlader commented Feb 3, 2016

shiftkey commented Feb 4, 2016

810 commented Feb 4, 2016

shiftkey commented Feb 4, 2016

810 commented Feb 4, 2016

shiftkey commented Feb 4, 2016

810 commented Feb 4, 2016

shiftkey commented Feb 4, 2016

shiftkey commented Feb 4, 2016

dscho commented Feb 4, 2016

dscho commented Feb 4, 2016

dscho commented Feb 4, 2016

oysteinkrog commented Feb 4, 2016

dscho commented Feb 4, 2016

810 commented Feb 4, 2016

dscho commented Feb 4, 2016

dscho commented Feb 5, 2016

oysteinkrog commented Feb 5, 2016