[Mono-bugs] [Bug 34263][Maj] New - mono hangs after an unhandled exception

bugzilla-daemon@rocky.ximian.com bugzilla-daemon@rocky.ximian.com
19 Nov 2002 14:37:58 -0000


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@ximian.com.

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

--- shadow/34263	Tue Nov 19 09:37:58 2002
+++ shadow/34263.tmp.5769	Tue Nov 19 09:37:58 2002
@@ -0,0 +1,47 @@
+Bug#: 34263
+Product: Mono/Runtime
+Version: unspecified
+OS: other
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Major
+Component: misc
+AssignedTo: dick@ximian.com                            
+ReportedBy: lupus@ximian.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: mono hangs after an unhandled exception
+
+This bug has been caused by the finalizer thread patch.
+Try running:
+class T {
+	static void Main() {
+		throw new System.Exception ();
+	}
+}
+mono prints the stack trace and then just hangs: the finalizer thread is
+still alive, waiting for an event to tell it to shut down.
+(gdb) bt
+#0  0x401ee671 in nanosleep () from /lib/libc.so.6
+#1  0x400f9809 in __pthread_timedsuspend_new () from /lib/libpthread.so.0
+#2  0x400f6397 in pthread_cond_timedwait_relative () from /lib/libpthread.so.0
+#3  0x400f6524 in pthread_cond_timedwait () from /lib/libpthread.so.0
+#4  0x0814fc4e in _wapi_handle_wait_signal_handle (handle=0x3) at
+handles.c:1081
+#5  0x08158ce2 in WaitForSingleObject (handle=0x3, timeout=4294967295) at
+wait.c:95
+#6  0x081196c1 in finalizer_thread (unused=0x0) at gc.c:392
+#7  0x081587b7 in timed_thread_start_routine (args=0x8201458) at
+timed-thread.c:94
+#8  0x400c2e1e in GC_start_routine () from /usr/lib/libgc.so.6
+#9  0x400f7048 in pthread_start_thread () from /lib/libpthread.so.0
+#10 0x400f708e in pthread_start_thread_event () from /lib/libpthread.so.0
+
+BTW: mono_gc_cleanup() is never used, I added it to mono_runtime_cleanup
+(), but I still get the hang.
+This makes running the regression tests harder, so it's major priority
+because we need to run the tests before the release.