Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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: Thu, 7 Aug 2003 21:34:53 -0400
From: Christopher Faylor <cgf-idd AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Win2k and cygwin memory leak
Message-ID: <20030808013453.GA9600@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <3F30D849 DOT 8D2AA00C AT itsec-ss DOT nl> <bgsa5k$39n$1 AT main DOT gmane DOT org> <3F324535 DOT B10AA62D AT itsec-ss DOT nl> <bgtree$r7r$1 AT main DOT gmane DOT org> <20030807154057 DOT GB1689 AT redhat DOT com> <3F327990 DOT 4050104 AT cs DOT york DOT ac DOT uk> <20030807181734 DOT GA3794 AT redhat DOT com> <bguh6i$gfo$1 AT main DOT gmane DOT org> <lfj5jv872n09om6agp21lgp8q85dnishim AT 4ax DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <lfj5jv872n09om6agp21lgp8q85dnishim@4ax.com>
User-Agent: Mutt/1.4.1i

On Thu, Aug 07, 2003 at 11:33:48PM +0100, Sam Edge wrote:
>Rolf Campbell <Endlisnis AT mailc DOT net> wrote in
><bguh6i$gfo$1 AT main DOT gmane DOT org>
>in gmane.os.cygwin on Thu, 07 Aug 2003 17:44:08 -0400:
>>Does windows claim to free all memory allocated by a process when it
>>exits?
>
>It does, even on unexpected terminations.  (Seg-faults and the like.)

Just like any non-toy OS in the last 30 years or so.  Even Windows 95
should behave properly in this regard.

>>What about cygwin shared memory?
>
>Unlike System V, Windows shared memory is transient.  Once all handles
>that reference it are closed Windows deallocates it.  And Windows
>closes all open handles for a process when the process exits, even if
>this was caused by an unexpected termination.
>
>So the Cygwin shared memory is automatically deallocated once the last
>Cygwin process exits, irrespective of any bugs (memory leaks) in
>Cygwin.
>
>Again, /supposedly/.  ;-)

All correct.  Supposedly is the operative word in the context that Windows
should be acting this way.  If it isn't acting this way, then it is pretty
clearly a Windows bug.
--
Please use the resources at cygwin.com rather than sending personal email.
Special for spam email harvesters: send email to aaaspam AT sourceware DOT org
and be permanently blocked from mailing lists at sources.redhat.com

--
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/