-
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
Error: Could not fork child process: Resource temporarily unavailable (-1).DLL rebasing may be required; see 'rebaseall / rebase --help'. #4375
Comments
I tried all the solutions for this issue... which I found on Internet.... But none of them could solve this issue on my computer. |
Tried these solutions.... None of them working... |
Maybe fill in a few details here would be a start? At the moment it is just a part time personal problem, rather than a full time professional activity.. [1]
[1] the original quote is from a redundancy / job hunt / career management course, but applies equally well here. |
All of those solutions revolve around ASLR, but that error message could be caused by various other things. It could be a cygheap mismatch, but that should be unlikely with v2.40.0. Have you tried rebasing like the message suggests? Did you check wether some other software is interfering with Git for Windows? See this list of known troublemakers. |
Still the similar error, for me too. |
for me too!( |
Y'all, there is way too little information provided in this report to do anything about it, so maybe instead of "me, too"ing, somebody could actually fill in the details, as asked for? |
@dscho At other configurations the problem reproduced too (64bit, 32bit; 7, 10 and maybe on future 55 and 666). Example:
Setup
Windows 7, same under 8. 32-bit.
Win 32 only PS C:\Users\User> $PSVersionTable PSVersion 5.1.14409.1005 Details
Bash
Stable work!
Periodically random error about forks, died unexpectedly, 0xC0000005, errno 11, retry: Resource temporarily unavailable ... (Cygwin.dll error on previous git bash versions with suggestion restart system every time.)
No, it is not about repositories. It's about broken build. |
@proxy-m please try to produce an actual MCVE. |
So, you still can not reproduce it... but continue closing issues about the problem. Strange. I get the error more often when try to start some script with many forks from Git Bash. |
Without a method of reproducing the problem, with some certainty, then it's not a problem that can be addressed by others who aren't seeing the same issues, hence the request for an MVCE. You indicate that "error more often when try start some script with many forks from Git Bash", so that is a good starter for you to create a test script that forces that situation. Then checking if it works on any other machines you can access. Once you have that MVCE, and some clarity on how to set up the machine (e.g. ancillary apps that need to be present), then others could have a look. I appreciate it is frustrating, but it's still a "fails elsewhere" problem without that MVCE. |
How many RAM do you have? Is your system distro language (i18n) English? |
Same here, Windows 11, also with latest git installed from https://git-scm.com/download/win. Previously worked installation did work till today. Not sure if that was Windows update or git package update that caused the error - I do update both frequently. |
Right, Cygwin (and as a consequence, MSYS2's runtime as well as Git for Windows' Bash) are incompatible with ASLR right now. As the original reporter ghosted us, I'll close this here ticket. |
Interesting... non-English Windows version again. |
I didn't make any changes to the default settings of Git setup....during installation.
Q - Any other interesting things about your environment that might be related
to the issue you're seeing?
Ans - I am not aware of anything & have no clue what is causing this issue in my Laptop.
Details
Ans - I'm using Git Bash, where I'm getting this error.
Q- What commands did you run to trigger this issue? If you can provide a
Minimal, Complete, and Verifiable example
this will help us understand the issue.
Ans - I didn't run any command to trigger this issue. I got this error in my Git Bash. When I started/opened it for the very 1st time.
Then, I searched about this issue on internet & found these solutions, So, I tried these solutions👇
I tried the solutions suggested here
Q - What did you expect to occur after running these commands?
Ans - First of all, I didn't get any chance to run any command in Git Bash because I'am getting this error from the very time I installed it in my laptop.
I tried solve this problem & searched about it on Internet found some solution/ commends to run in the terminal/powershell. So, I tried those methods but they also didn't work.
Here is the link to those solutions which I found on internet-
I tried the solutions suggested here
I expected that Git Bash will start working normally. But it didn't work.
Q - What actually happened instead?
Ans - Nothing Happened.
Q - If the problem was occurring with a specific repository, can you provide the
URL to that repository to help us with testing?
Ans - This problem is not occurring with a specific repository whereas It is a problem that is not allowing me write a single command in my Git Bash for the very 1st time since I installed it in my Laptop.
The text was updated successfully, but these errors were encountered: