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

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

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

--- shadow/77856	2006-03-20 09:33:39.000000000 -0500
+++ shadow/77856.tmp.15633	2006-03-20 10:00:51.000000000 -0500
@@ -1,17 +1,17 @@
 Bug#: 77856
 Product: Mono: Runtime
 Version: 1.1
-OS: 
+OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Critical
-Component: misc
-AssignedTo: mono-bugs at ximian.com                            
+Component: io-layer
+AssignedTo: dick at ximian.com                            
 ReportedBy: drichard at largo.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
 URL: 
 Cc: 
 Summary: Mono Runtime Is Leaking Semaphores
@@ -36,6 +36,16 @@
 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.
+
+------- Additional Comments From dick at ximian.com  2006-03-20 10:00 -------
+It's correct that a semaphore is allocated and not released when mono
+exits.
+
+Whenever (either concurrently or consecutively) any other mono
+application is run by the same user, the same semaphore will be
+reused.  The ID to this semaphore is stored in a file in ~/.wapi which
+holds shared state.  This semaphore is used for cross-process
+synchronisation in the windows api emulation layer.