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 X-Injected-Via-Gmane: http://gmane.org/ To: cygwin@cygwin.com From: Joe Buehler Subject: Re: Process hang(100% CPU Usage) when concurrent calling select(),cygwin1.5.5-1 WinXP/Win2000 Date: Fri, 07 Nov 2003 10:44:20 -0500 Organization: Spirent Communications, Inc. Lines: 12 Message-ID: <3FABBDD4.6090900@hekimian.com> References: Reply-To: jbuehler@hekimian.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en In-Reply-To: X-Enigmail-Version: 0.76.7.0 X-Enigmail-Supports: pgp-inline, pgp-mime zhouxin wrote: > If the udp worker's count greater than 18,some thread's select() hang and process > take 100% cpu: My vague recollection is that Cygwin allocates threads to handle select(). Interestingly, there is a static pool of 18 threads internally before switching to dynamically created threads. So there may be some problem related to the dynamically allocated threads code. -- Joe Buehler -- 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/