Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@sources.redhat.com>
List-Help: <mailto:cygwin-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@sources.redhat.com
Delivered-To: mailing list cygwin@sources.redhat.com
Message-Id: <4.3.2.7.2.20011011110411.00b79700@san-francisco.beasys.com>
X-Sender: andyp@san-francisco.beasys.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 11 Oct 2001 11:06:21 -0700
To: Charles Wilson <cwilson@ece.gatech.edu>
From: Andy Piper <andyp@bea.com>
Subject: Re: More problems with subprocesses in 1.3.3
Cc: cygwin@cygwin.com
In-Reply-To: <3BC5DBF2.7080705@ece.gatech.edu>
References: <4.3.2.7.2.20011009125357.00b61b50@san-francisco.beasys.com>
 <4.3.2.7.2.20011011094427.00b7bc60@san-francisco.beasys.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 01:50 PM 10/11/01 -0400, Charles Wilson wrote:
>Ugh.  That's not normal.  (Honest!  We wouldn't release a kernel with a 
>bug like that if we knew about it -- and many many folks have been using 
>1.3.3 on NT for months now without any reports like yours.)
>
>Is there something unique about your machine, or your usage patterns? 
>(e.g. do you do everything from an XEmacs subshell, thus exercising the 
>fork/exec code more heavily than "normal", etc etc?)

Lots of fork and exec. I am running two large java processes (200Mb each) 
from within shell scripts in a bash shell. They also pump out a lot of 
output. The whole machine freezes midway through the run. The cursor still 
works though so I would guess that either all the CPU is taken or all the 
memory. My machine has 1Gb of virtual memory.

andy



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

