[Mono-bugs] [Bug 81856][Nor] Changed - Dead Lock with mysql

[bugzilla-daemon at bugzilla.ximian.com]

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 james at stev.org.

http://bugzilla.ximian.com/show_bug.cgi?id=81856

--- shadow/81856	2007-07-16 10:48:14.000000000 -0400
+++ shadow/81856.tmp.6731	2007-07-16 11:08:13.000000000 -0400
@@ -255,6 +255,39 @@
 result of SuppressFinalizer in the Timer.cs Dispose method).
 Another thread was inside a sigusr1 signal handler and stuck
 in the mono_domain_lock call in mono_jit_info_table_find().
 Using a lock-free mono_jit_info_table_find() allows the program to
 continue for hundreds of thousands of iterations at least
 (I just stopped it after a few minutes).
+
+------- Additional Comments From james at stev.org  2007-07-16 11:08 -------
+This too will also cause a deadlock in the same way for me but without
+the mysql libs being involved.
+
+	class Temp {
+		public void Run() {
+			while (true)
+				Thread.Sleep(1000);
+		}
+	}
+
+	class Program {
+		static void Main(string[] args) {
+			try {
+				Thread Thd;
+				Temp Tmp = new Temp();
+				int i = 0;
+
+				while (true) {
+					Thd = new Thread(new ThreadStart(Tmp.Run));
+					Thd.Start();
+					Thd.Abort();
+
+					Console.WriteLine(" Count = " + i);
+					i++;
+				}
+
+			} catch (Exception e) {
+				Console.WriteLine(e.Message);
+			}
+			Console.WriteLine("Exiting");
+		}