[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 lupus at ximian.com.

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

--- shadow/81856	2007-07-16 09:11:07.000000000 -0400
+++ shadow/81856.tmp.6338	2007-07-16 10:48:14.000000000 -0400
@@ -244,6 +244,17 @@
 thread -1211114848 from TLS
 ** Message: _wapi_thread_abandon_mutexes: Thread 0x127639 abandoning
 held mutexes
 ** Message: _wapi_thread_set_termination_details: Recording thread
 handle 0x127639 id -1365808208 status as -1
 
+
+------- Additional Comments From lupus at ximian.com  2007-07-16 10:48 -------
+gdb is not very useful for me, because it doesn't produce backtraces.
+I decode a couple of stack dumps and one seemd stuck in the
+mono_domain_lock() in object_register_finalizer() (seemigly as the
+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).