Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com From: Sam Edge To: cygwin@cygwin.com Subject: Re: Win2k and cygwin memory leak Date: Thu, 07 Aug 2003 23:33:48 +0100 Organization: . Reply-To: cygwin@cygwin.com Message-ID: References: <3F30D849.8D2AA00C@itsec-ss.nl> <3F324535.B10AA62D@itsec-ss.nl> <20030807154057.GB1689@redhat.com> <3F327990.4050104@cs.york.ac.uk> <20030807181734.GA3794@redhat.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Posting-Agent: Hamster/2.0.0.1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id h77MYKW16331 Rolf Campbell wrote in 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.) > 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/. ;-) Regards, -- Sam Edge -- 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/