Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-Injected-Via-Gmane:	http://gmane.org/
To:	cygwin AT cygwin DOT com
From:	Joe Buehler <jbuehler AT hekimian DOT com>
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:	<E1AH1u4-0003nc-00 AT quimby DOT gnus DOT org>
Reply-To:	jbuehler AT hekimian DOT com
Mime-Version:	1.0
X-Complaints-To:	usenet AT sea DOT gmane DOT 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:	<E1AH1u4-0003nc-00@quimby.gnus.org>
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/

- Raw text -