From: Konstantin Khomoutov <kostix+git@007spb.ru>
To: "Vacha, Brian [USA]" <vacha_brian@bah.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Fork Errors
Date: Thu, 6 Oct 2016 17:40:41 +0300 [thread overview]
Message-ID: <20161006174041.4225c2b52bd144e5b3db8a85@domain007.com> (raw)
In-Reply-To: <2E2ADD8A4AA3FA44A8D8FB00E2B24154B5E9E1C6@ASHBDAG1M3.resource.ds.bah.com>
On Thu, 6 Oct 2016 14:02:09 +0000
"Vacha, Brian [USA]" <vacha_brian@bah.com> wrote:
> When starting Git Bash, I receive the following errors:
> 0 [main] bash 18088 fork: child 14072 - died waiting for dll loading,
> errno 11 bash: fork: retry: No child processes
> 1190419 [main] bash 18088 fork: child 8744 - died waiting for dll
> loading, errno 11 bash: fork: retry: No child processes
> 3343518 [main] bash 18088 fork: child 12324 - died waiting for dll
> loading, errno 11 bash: fork: retry: No child processes
> 7480858 [main] bash 18088 fork: child 17008 - died waiting for dll
> loading, errno 11 bash: fork: retry: No child processes
> 15635036 [main] bash 18088 fork: child 8108 - died waiting for dll
> loading, errno 11 bash: fork: Resource temporarily unavailable
> bash-4.3$
>
> My connection is great at 72 Mbps download and 93 Mbps upload. I
> don't receive other errors so it appears to be a Git Bash issue to me.
Have you tried searching through Git for Windows bugtracker [1] for
your problem. I'm pretty sure it was recently discussed there.
The issue #776 [2] looks like the one you're experiencing.
1. https://github.com/git-for-windows/git/issues
2. https://github.com/git-for-windows/git/issues/776
next prev parent reply other threads:[~2016-10-06 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 14:02 Fork Errors Vacha, Brian [USA]
2016-10-06 14:40 ` Konstantin Khomoutov [this message]
2016-10-13 13:45 ` [External] " Vacha, Brian [USA]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161006174041.4225c2b52bd144e5b3db8a85@domain007.com \
--to=kostix+git@007spb.ru \
--cc=git@vger.kernel.org \
--cc=vacha_brian@bah.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).