Please do not reply to this email- if you want to comment on the bug, go to the URL shown below and enter your comments there.
Changed by [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=76254 --- shadow/76254 2005-09-30 14:20:45.000000000 -0400 +++ shadow/76254.tmp.32751 2005-09-30 14:35:01.000000000 -0400 @@ -100,6 +100,22 @@ ------- Additional Comments From [EMAIL PROTECTED] 2005-09-30 14:20 ------- Have you seen the individual thread problems I noted in version 1.1.9.1? I was wondering if there might be a problem with the threads not having their parents properly set. I don't know linux threads well enough to know if this is an issue. + +------- Additional Comments From [EMAIL PROTECTED] 2005-09-30 14:35 ------- +I'm not 100% sure I understand your last comment. + +Yes, I can duplicate the (near-)endless loop using IE - but I fail to +see how this relates with the thread parent. The loop simply can't +finish unless (a) the handshake complete or (b) the socket timeout. +Clicking rapidely in IE starts a new thread, leaving the original +connection "suspended" - no more data is sent to end the handshake +(like an SSL alert) nor is the socket closed properly. + +The CPU usage is high because the loop is looping without waiting for +anything (and without being nice and letting go of the CPU). + +The main difference with 1.1.9.x is that the async code is now using +the threadpool. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
