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=79457 --- shadow/79457 2006-10-06 14:01:32.000000000 -0400 +++ shadow/79457.tmp.25609 2006-11-13 18:07:42.000000000 -0500 @@ -211,6 +211,19 @@ ------- Additional Comments From [EMAIL PROTECTED] 2006-10-06 14:01 ------- Seems to happen if we leave threads running before exiting main and threads are actively running and using AutoResetEvents, ManualResetEvents, etc... + +------- Additional Comments From [EMAIL PROTECTED] 2006-11-13 18:07 ------- +I've been unable to reproduce this with current svn. I've tested on +several machines, to see if variations in cpu speed showed a race +condition. + +On which version of mono exactly are you seeing the bug? + +If it happens again, running "mono --wapi=seminfo" should show the PID +of the mono process that is holding the semaphore locked. Getting a +backtrace of that process should show what's causing it. (If your +mono installation is too old to have that option, it's also older than +several fixed bugs of this variety.) _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
