This is the mail archive of the
mailing list for the Cygwin project.
RE: Has anyone collected a summary of cygwin vs Windows 7 64 bit outstanding issues?
- From: Bill Ross <photoriot at yahoo dot com>
- To: "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Wed, 23 May 2012 09:26:50 -0700 (PDT)
- Subject: RE: Has anyone collected a summary of cygwin vs Windows 7 64 bit outstanding issues?
- Reply-to: Bill Ross <photoriot at yahoo dot com>
On 5/23/2012 9:24 AM, Larry W. Virden wrote:
> We are trying to make use of cygwin in several ways
on Windows 7
> 64-bit desktops.
> One of the first things we have noticed is that
there are a lot of
> processes sitting on the desktop that appear to be
related to cygwin
> that we didn't see previously on 32 bit XP.
> For instance, if we open a bash console, perform an
ssh to another
> machine, do some work, then close the window, the
bash and ssh still
> seem to be listed when we look at the windows 7 task
I have 64-bit Win7 with cygwin, and after a while this
sort of thing runs out of resources (errno 11) until I reboot (and then starts
up after a few ok runs, as just now):
$ find . -name "*.java" | while read i ; do
> echo %%%% $i >> x
> grep foob $i >> x
375832787 [main] -bash 6020 fork: child -1 - forked
process died unexpectedly, retry 0, exit code -1073741819, errno 11
-bash: fork: retry: Resource temporarily unavailable
-bash: fork: Resource temporarily unavailable
And I think I have noticed lots of bash processes hanging
around, though not in this instance.
$ uname -a
CYGWIN_NT-6.1-WOW64 mybox 1.7.13(0.260/5/3) 2012-04-05
12:43 i686 Cygwin
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple