Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sat, 09 Aug 2003 19:52:54 +0200 From: Yorick Koster Subject: Re: Information regarding problem when Windows cannot re-use PID numbers In-reply-to: <20030809175354.GC9863@redhat.com> To: cygwin AT cygwin DOT com Message-id: <3F3534F6.7000008@itsec-ss.nl> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-MailScanner-Information: Please contact helpdesk AT quicknet DOT nl for more information X-MailScanner: Found to be clean References: <3F344008 DOT 00000D DOT 07740 AT pantene DOT yandex DOT ru> <3F353229 DOT 2060600 AT itsec-ss DOT nl> <20030809175354 DOT GC9863 AT redhat DOT com> 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. > > We have not yet looked at RAMpage. Our main focus was solving the problem, not to find a workaround. I'll also try this monday. 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/