Win2k and cygwin memory leak

Fri Aug 8 01:42:00 GMT 2003

On Thu, Aug 07, 2003 at 11:33:48PM +0100, Sam Edge wrote:
>Rolf Campbell <Endlisnis@mailc.net> wrote in
><bguh6i$gfo$1@main.gmane.org>
>in gmane.os.cygwin on 2003年8月07日 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@sourceware.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/