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: Mon, 5 Aug 2002 18:01:18 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: _exit() missing WSACleanup() call? Message-ID: <20020805180118.I3921@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <200208051623 DOT 58635 DOT juergen AT pullmoll DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200208051623.58635.juergen@pullmoll.de> User-Agent: Mutt/1.3.22.1i On Mon, Aug 05, 2002 at 04:23:45PM +0200, Juergen Buchmueller wrote: > every child that inherits a socket handle - but the CYGWIN libc > implementation does not seem to call WSACleanup() during the _exit() function > cleanup in that case? > > The effect is that after a few minutes, after maybe 100 child processes were > forked and exited again, Windows does something on a severity scale between > displaying message boxes about a lack of resources to hard lockups with > faults in 'kernel32.dll'. I'm lost. > > I tried to WSACleanup() in my user osd_exit() function to no avail. My best > guess is that there are other resources which I cannot give free this way? When calling WSACleanup() in your application doesn't help, it's somewhat likely that the problem is actually in your code. What is the parent process doing with the sockets? Is it surely closing and (perhaps) shutting them down properly? Did you look for netstat output? > The same project runs fine for days on various FreeBSD and GNU/Linux systems. That's actually not good an example. The socket implementation is *waaayyyy* cleaner in BSD and Linux than is Winsock. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/