RE: Process hang(100% CPU Usage) when concurrent calling select(),cygwin1.5.5-1 WinXP/Win2000

2003-11-11 Thread Bakken, Luke
The latest snapshot also appears to fix one of the two rsync problems I was experiencing. Problem 1: rsync -av /foo/ /bar/ always hangs at the end of copying files when /bar doesn't exist - fixed Problem 2: rsync -av /foo/ /bar/ always hangs at the end of copying files when /bar already has files

Re: Process hang(100% CPU Usage) when concurrent calling select(),cygwin1.5.5-1 WinXP/Win2000

2003-11-11 Thread D. N. Knisely
Just thought that I would report that the 1108 snapshot also solved a similar problem with privoxy using 100% of CPU (also apparently on select, which is basically where that program spins all the time) occasionally under high load.  I wanted to test for a few days to make sure it was gone.  Thanks

Re: Process hang(100% CPU Usage) when concurrent calling select(),cygwin1.5.5-1 WinXP/Win2000

2003-11-09 Thread zhouxin
Yeah,it seems all ok! >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,

Re: Process hang(100% CPU Usage) when concurrent calling select(),cygwin1.5.5-1 WinXP/Win2000

2003-11-08 Thread Christopher Faylor
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

Re: Process hang(100% CPU Usage) when concurrent calling select(),cygwin1.5.5-1 WinXP/Win2000

2003-11-07 Thread Christopher Faylor
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 t

Re: Process hang(100% CPU Usage) when concurrent calling select(),cygwin1.5.5-1 WinXP/Win2000

2003-11-07 Thread Joe Buehler
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

Process hang(100% CPU Usage) when concurrent calling select(),cygwin1.5.5-1 WinXP/Win2000

2003-11-04 Thread zhouxin
hi,all I have reported this problem a week ago.I belive that the test_select.c(see below) is correct.The usage of select() is classical. This testing program initialize a number of threads, each thread create a socket and send UDP packet to UDP server,then wait response by calling selec