[Mono-bugs] [Bug 76574][Maj] New - Experiencing hangs trying to do IO in 1.1.9

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Thu Oct 27 14:28:13 EDT 2005

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.


--- shadow/76574	2005-10-27 14:28:13.000000000 -0400
+++ shadow/76574.tmp.8590	2005-10-27 14:28:13.000000000 -0400
@@ -0,0 +1,46 @@
+Bug#: 76574
+Product: Mono: Runtime
+Version: 1.1
+OS Details: 
+Status: NEW   
+Priority: Major
+Component: io-layer
+AssignedTo: dick at ximian.com                            
+ReportedBy: joeshaw at novell.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+Summary: Experiencing hangs trying to do IO in 1.1.9
+This bug started happening in mono 1.1.9, and continues with
+After running Beagle for a long time, it will eventually stop indexing
+data.  After the bug manifests itself, any mono app which is subsequently
+executed that tries to do IO hangs, including all of the beagle utilities
+and mcs.
+During a typical beagle run there are two processes running, each of which
+have one unix domain socket open, which responds to data sent to it.  One
+is the beagled and one is the index helper.  In this particular run (I
+don't know if it's every time or not), the index helper is the one that's
+hung.  Using socat to connect to the unix domain socket, sending messages
+to beagled is handled and a response is returned.  Nothing happens when
+contacting the index helper.
+This bug is being pretty widely reported by our users on IRC, and it seems
+to happen reliably for me, but it takes quite some time to happen.  In my
+particular run, it was on the 13th invocation of the index helper.  This
+index helper had itself been running for nearly 5 and a half minutes.  It
+had been about an hour and a half since the beagle daemon was started.  So
+distilling it down into a test case isn't really feasible.
+I'm attaching a few things:
+* The stack traces of the index helper, which is hung and not responding to
+* The strace output of an mcs run, which hangs.  All mono apps hang on the
+same semop(), although the files being opened vary from app to app.

More information about the mono-bugs mailing list