[Mono-bugs] [Bug 75007][Maj] New - Hang in constructor

[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 joeshaw at novell.com.

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

--- shadow/75007	2005-05-20 13:19:05.000000000 -0400
+++ shadow/75007.tmp.16861	2005-05-20 13:19:06.000000000 -0400
@@ -0,0 +1,33 @@
+Bug#: 75007
+Product: Mono: Runtime
+Version: 1.1
+OS: 
+OS Details: On mono 1.1.7.x
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Major
+Component: JIT
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: joeshaw at novell.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Summary: Hang in constructor
+
+Sorry, I'm not sure if this is a JIT bug or an IO layer bug.
+
+With the new messaging system we're using in Beagle, we are frequently
+getting hangs in a constructor for a class which handles socket connections
+on a Unix domain socket.  The constructor itself is very simple, it just
+sets one field based on its parameters -- one line.  We've tested 1.1.7 and
+all the 1.1.7.x releases.  It happens on all of them, but not on 1.1.4 or
+1.1.6 (but does on 1.1.6.2, apparently).  It's serious enough that we feel
+we can't release the next version of Beagle without a resolution.
+
+Here's the interesting bit: after it hangs I attach gdb to it.  I try
+calling mono_print_method_for_ip() on some of the unknown stack frames, and
+it hangs on all of them.  So maybe this is an internal locking problem?
+
+I'll attach the stack traces.  For some reason 'thread apply all bt' didn't
+quite work.