-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Launching git bash gives bash fork retry error #776
Comments
Unfortunately this report does not give me enough information to even try to reproduce the problem, which would be required before I could try to diagnose and fix the bug. |
@dscho Here is how I can reproduce this locally:
|
I'm somewhat convinced this is due to some corporate antivirus / security software on our Win7 machines, which for whatever reason only has an issue with git >= 2.7.0.2. Reading the change log it might have something to do with DEP/ASLR, but I don't know enough about that to be sure. Possibly related #649, which also mentions corporate antivirus. |
I have the same error coming from corporate devices. Multiple people are running 2.6.1 and earlier and not having issues, but anyone who is trying to install latest release (2.8.4 as of this post) is having this error which crashes the window if they try to execute anything from the bash window. Is there a way to download previous versions which have been fully packaged? |
https://github.com/git-for-windows/git/releases |
Do you have cygwin installed? I had similar problems with both cygwin and git-for-windows installed if they were both using the same architecture (e.g. both 64-bit versions). My workaround was to use the 64-bit version of cygwin and the 32-bit version of git. |
@cs96and No cygwin on my machine. |
I am fairly convinced that the prerelease, as well as the version v2.10.1 (due later today), fix this issue, as I suspect that domain accounts are in use. Please test as soon as you can. |
I had the same problem, the installer under @dscho's link resolved my problem, thanks a lot! |
Just tried both prerelease-v2.10.0.windows.1.11.geda474c and v2.10.1. Problem still exists, same as before. Reverted back to v2.7.0. |
@novabe please fill out the issue reporting template so I have more information to work with, then. |
Setup
$ git --version --build-options
$ cmd.exe /c ver
One of the following:
Details
|
This looks very similar to #910 (it's also Windows 7..). Maybe there is another application interfering with the MSYS2 runtime, similar to PowerBroker, that is still running (see https://cygwin.com/faq/faq.html#faq.using.bloda for an incomplete list)? In any case, it would be good if you could test whether Cygwin works (our MSYS2 runtime is a close fork of Cygwin's runtime, therefore we inherit all those issues...). |
The FAQ you reference say that some of the applications interfere even after they have been deactivated, so it may still be PowerBroker. @OverlordQ in #649 said he stopped it by renaming a dll, which may work better. I'm not comfortable trying that. I tried to install Cygwin, and I got similar installation errors as those shown in #910. Trying to run the shell after give different errors from git bash and a non-functional shell. I've attached the logs below. Shell startup messages, and attempt to run
End of installation log:
I blame PowerBroker. |
That looks like your |
My So then it may seem like I don't get the fork error with cygwin. |
I also had the same problem and it went away when I installed v2.7.0. |
@hmusavi are you also on Windows 7? |
@dscho yes. The error only happens on my Windows 7 machine. I have Windows 10 as well and that issue does NOT occur with the latest Git version. |
I tried to reproduce the bug, installing Windows 7 into a VM. I do not get that error. Maybe I have to install PowerBroker to reproduce the problem? But that would be quite an unreasonable burden on me, given that I have to take care of so many other tickets that are still open, I am sure you understand. |
Thank you @dscho! I understand. You are probably correct to assume that PowerBroker is the culprit. I do have PowerBroker running on my Windows 7 machine. |
@hmusavi and there is no chance you can disable it temporarily just to make sure that it is the issue, eh? |
I'm afraid not easily. Corporate policy. I'll see if I can have our IT department to disable it temporarily so I could do the test and then re-enable it. I'll get back to you but it may take a while. |
@hmusavi: Note that disabling might not be enough, you might need to uninstall it. See posts earlier in the thread. |
If you have access to modify your registry, if you navigate to This was the workaround discovered when I worked with BeyondTrust trying to diagnose the issue. (Sorry for the double post, commented under wrong account) |
I have the same problem; As soon as I added the the git install dir to ExcludedProfilerApps it worked. |
Excellent! Thank you for sharing this solution! |
Thank you @OverlordQ for your post. The workaround/solution works perfectly. |
Under the assumption that PowerBroker was also at fault for the original poster, and that the workaround helps, I close this ticket. |
It helps, but not really a good solution as - at least mine - BeyondTrust resets the registry entry after approx 60 min. |
Sorry that it is not an ideal solution. If you figure out what broke in git-for-windows/msys2-runtime@4c36272...84870b7 (reflecting the change in the |
I'll try to find some free time and see if I can figure out a way to do an automated bisect. |
I have the same output and issue on my work machine - I downgraded to 2.7.0 as suggested and that worked flawlessly, but apparently policy dictates that git be no older than 2.7.3 because reasons, so I was forced to "upgrade" - 2.7.3 worked still, barring some permissions issues on first run (separate, less critical, issue), so I decided to bisect all the releases of GFW until current and found that 2.9.3.2 is the highest version that doesn't give the fork error, 2.9.3.3 (pre-release) is when it starts happening for me. Note: I have neither BeyondTrust/PowerBroker installed, nor the specific antivirus mentioned in the linked thread, though I'm not discounting corporate antivirus as a possibility. |
Could you compare the |
The error text is:
This prevents at least git-stash from working:
I have tested different versions of git, and found that anything above 2.7.0 exhibits this problem for me and my coworkers (the problem starts with 2.7.0.2).
I also found http://stackoverflow.com/questions/37263702/cant-start-git-bash which implies it might be antivirus related. Creating this issue to confirm if others have experienced it, and if we know this to be antivirus related, I hope someone can recommend what to whitelist? Is it just "C:\Program Files\Git\usr\bin\bash.exe"?
The text was updated successfully, but these errors were encountered: