Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <3F37704B.E570EFD4@ITsec-SS.nl>
Date: Mon, 11 Aug 2003 12:30:36 +0200
From: Yorick Koster <Y.Koster@ITsec-SS.nl>
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Information regarding problem when Windows cannot re-use PID numbers
References: <3F344008.00000D.07740@pantene.yandex.ru> <3F353229.2060600@itsec-ss.nl> <20030809175354.GC9863@redhat.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Christopher Faylor wrote:

> On Sat, Aug 09, 2003 at 07:40:57PM +0200, Yorick Koster wrote:
> >Rogier & I have been busy trying to isolate the memory leak problem we
> >have encountered on Win2k machines. A lot of people on this list have
> >suggested this is in fact a Win2k problem. We have indeed verified this
> >is indeed not a CygWin issue, but I am not totally convinced this is a
> >Windows problem. The following command can be used to reproduce the leak:
> >
> >FOR /L %a IN (1,1,65535) DO echo exit | cmd
>
> The above would certainly rule out cygwin then since there isn't any cygwin
> component.
>
> Does RAMpage "fix" this problem, assuming you can even run it?  If so,
> that would indicate a memory fragmentation problem rather than a lack
> of memory problem.

I have tried the RAMpage "fix", however it does not seem to work. When ever I
run RAMpage, it does seem to slow down the process, but eventually all memory
will become unavailable for newly started processes. Uninstalling Outpost
actually did the trick.

Regards,
Yorick


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/