[Mono-bugs] [Bug 81476][Wis] Changed - Thread.Start() deadlock
bugzilla-daemon at bugzilla.ximian.com
bugzilla-daemon at bugzilla.ximian.com
Sat Apr 28 09:47:34 EDT 2007
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 robertj at gmx.net.
http://bugzilla.ximian.com/show_bug.cgi?id=81476
--- shadow/81476 2007-04-28 08:09:35.000000000 -0400
+++ shadow/81476.tmp.8728 2007-04-28 09:47:34.000000000 -0400
@@ -10,13 +10,12 @@
Component: CORLIB
AssignedTo: mono-bugs at ximian.com
ReportedBy: alan.mcgovern at gmail.com
QAContact: mono-bugs at ximian.com
TargetMilestone: ---
URL:
-Cc:
Summary: Thread.Start() deadlock
Running the following testcase on mono results in a deadlock 99% of the
time. I tracked the problem down to calls to Thread.Start() never
returning. The problem isn't part of the Timer code, but it does highlight
the issue.
@@ -96,6 +95,16 @@
Thread 0 Starting
Thread 2 Starting
Thread 3 Starting
Thread 9 Starting
Thread 7 Starting
Thread 4 Starting
+
+------- Additional Comments From robertj at gmx.net 2007-04-28 09:47 -------
+Oops, my XP machine was not on SVN HEAD. Now I can confirm the issue,
+but it's by no means a deadlock in Thread.Start.
+If I insert a Console.ReadLine () just before the end of Main (),
+the test case is running perfectly, so it's probably "just" a
+termination issue.
+
+Can someone confirm that?
+
More information about the mono-bugs
mailing list