This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Process hang(100% CPU Usage) when concurrent calling select(),cygwin1.5.5-1 WinXP/Win2000
- From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Sat, 8 Nov 2003 15:51:43 -0500
- Subject: Re: Process hang(100% CPU Usage) when concurrent calling select(),cygwin1.5.5-1 WinXP/Win2000
- References: <E1AH1u4-0003nc-00@quimby.gnus.org> <3FABBDD4.6090900@hekimian.com> <20031107182429.GA3490@redhat.com>
- Reply-to: cygwin at cygwin dot com
On Fri, Nov 07, 2003 at 01:24:29PM -0500, Christopher Faylor wrote:
>On Fri, Nov 07, 2003 at 10:44:20AM -0500, Joe Buehler wrote:
>>zhouxin wrote:
>>>If the udp worker's count greater than 18,some thread's select() hang
>>>and process take 100% cpu:
>>
>>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.
>
>Hmm. Interesting observation. I took a stab at fixing a couple of
>obvious problems in the thread overflow code. It seems like it might
>have solved the problem.
>
>There will be a new snapshot available in an hour or so at:
>
>http://cygwin.com/snapshots/
>
>Thanks for the test case, btw.
So... did the snapshot fix the problem?
cf
--
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/