This is the mail archive of the
mailing list for the Cygwin project.
Re: bash "Couldn't Allocate Heap" error - info.
Antony Baxter wrote:
This afternoon, for the first time, I began
C:\cygwin\bin\bash.exe: *** fatal error - couldn't
allocate heap ....
... child_copy: stack write copy failed,...
errors that have been reported on this list before. I
am getting these errors on every '#! /bin/bash'
script, though I can initially open a bash shell.
I tried changing the heap sizes, and tried rebaseall -
neither made a difference.
Earlier today I had installed the drivers for my new
Logitech webcam. Suspecting that these might be the
problem, I killed all the Logitech processes,
restarted all my Cygwin services, restarted Cygwin/X,
and lo & behold, all the errors disappeared and
everything worked fine.
It'd be great to get these to work together, but not
the end of the world if its not possible. Any
Thank you Thank you Thank you! That's it exactly. I was wondering why
my Cygwin/X stuff started behaving badly. Unfortunately, I had just done
a big update, so I blamed that for awhile. But this is definitely it.
And after much experimentation, I think you just need to stop one file
from running. I'm not sure what was causing it to run, as it wasn't in
any of my startup folder. But if you rename
to something else (I called it LVPrcSrv.exe.old), Cygwin/X starts working
again, and there is no loss of functionality that I can tell.
Jonathan Arnold (mailto:firstname.lastname@example.org)
Jiggle The Handle, a personal blog http://jiggle.anaze.us
Procrastination is the art of keeping up with yesterday.
- Don Marquis
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html