[Mono-bugs] [Bug 77856][Cri] New - Mono Runtime Is Leaking Semaphores

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Mon Mar 20 09:33:39 EST 2006

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 drichard at largo.com.


--- shadow/77856	2006-03-20 09:33:39.000000000 -0500
+++ shadow/77856.tmp.15252	2006-03-20 09:33:39.000000000 -0500
@@ -0,0 +1,41 @@
+Bug#: 77856
+Product: Mono: Runtime
+Version: 1.1
+OS Details: 
+Status: NEW   
+Priority: Critical
+Component: misc
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: drichard at largo.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+Summary: Mono Runtime Is Leaking Semaphores
+This is a major issue that is holding up the migration of the City of Largo
+to Evolution 2.6.  Evolution is with mono in the 2.6 version.
+mono-core-   When you invoke a mono application such as
+Tomboy or Evolution 2.6, it uses a semaphore and creates an entry
+apparently in /dev/shm which is detected with ipcs -s.
+When the mono program is closed, the semaphore is never released.  This
+leaking issue causes the server to run out of server wide semaphores and
+then fail to allow additional process.  Tuning isn't going to help because
+they are leaking.
+Here is proof:
+oa3:~ # ps -ef | grep teachers
+root      1332   887  0 09:21 pts/1    00:00:00 grep teachers
+oa3:~ # ipcs -s | grep teachers
+0x4d02f3e0 524304     teachers  600        8         
+oa3:~ # 
+Nothing is running for teachers, yet the semaphore has leaked.  Semaphore
+was not in use before mono applications (tomboy in this case) was run.
+We are basically down.

More information about the mono-bugs mailing list