From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: MS-Informatique <info@ms-informatique.be>
Cc: git@vger.kernel.org
Subject: Re: Bug report Windows 10
Date: Mon, 10 Aug 2015 15:05:06 +0200 [thread overview]
Message-ID: <16cbfe1f65f82104d084ce9626be7097@www.dscho.org> (raw)
In-Reply-To: <017101d0d367$d2009490$7601bdb0$@ms-informatique.be>
Hi,
On 2015-08-10 14:26, MS-Informatique wrote:
> My Windows notebook got updated to Windows 10 and now my Git Bash doesn't
> start and when I open an existing repository from Git Gui, I am getting next
> error:
> "0 [main] us 0 init_cheap: VirtualAlloc pointer is null, Win32 error 487
> AllocationBase 0x0, BaseAddress 0x68570000, RegionSize 0x410000, State
> 0x10000
> C:\Program Files (x86)\Git\bin\sh.exe: *** Couldn't reserve space for
> cygwin's heap, Win32 error 0"
>
> I am running GIT version 1.9.5 (latest build for Windows).
>
> Can someone help me?
First of all, the home page of Git for Windows has hints where to report bugs (and where to look for possible resolutions first).
Second, this issue is so common that I wrote a wiki page about it: https://github.com/git-for-windows/git/wiki/32-bit-issues
Short version: reinstall Git for Windows. Preferably a 64-bit Git for Windows 2.x from https://git-for-windows.github.io/. And you might want to heed the advice given in http://git-for-windows.github.io/#contribute when you want to report bugs ;-)
Ciao,
Johannes
prev parent reply other threads:[~2015-08-10 13:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 12:26 Bug report Windows 10 MS-Informatique
2015-08-10 12:34 ` Konstantin Khomoutov
2015-08-10 13:05 ` Johannes Schindelin [this message]
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=16cbfe1f65f82104d084ce9626be7097@www.dscho.org \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=info@ms-informatique.be \
/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).