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 Message-ID: <004601c50647$b3dce4d0$173ca8c0@AlohaSunset.com> From: "Mark Pizzolato" To: References: <20050129203607 DOT GA21386 AT trixie DOT casa DOT cgf DOT cx> Subject: Re: pthreads leaks handles and threads when threads use sockets Date: Sat, 29 Jan 2005 13:15:45 -0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 29 Jan 2005 21:15:50.0288 (UTC) FILETIME=[B53A7900:01C50647] X-IsSubscribed: yes On Saturday, January 29, 2005 at 12:36 PM, Christopher Faylor wrote: > On Fri, Jan 28, 2005 at 09:09:31AM -0800, Mark Pizzolato wrote: > >I've been using clamav's clamd under cygwin and noticed that over time > >the > >handle count as viewed with TaskManager seems to grow to arbitrary > >values. > > This should be fixed in the latest snapshot. Corinna tracked this down to > the offending line of code and I made a change which should fix the > behavior. > > Thanks for the test case. It helped a lot in tracking this problem down. Thanks for the fix to the handle leakage. It works for me cleanly now. Any clue as to why there seems to be some bounded thread leakage (i.e. extra threads are created and persist for each thread in the test case which uses sockets concurrently)? Bounded leakage we can llive with, but I'm still curious. - Mark Pizzolato -- 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/