[Mono-bugs] [Bug 81727][Nor] New - Semaphore.Close does not free the OS handle

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Thu May 24 09:45:16 EDT 2007

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 jonathan.gagnon at croesus.com.


--- shadow/81727	2007-05-24 09:45:16.000000000 -0400
+++ shadow/81727.tmp.30276	2007-05-24 09:45:16.000000000 -0400
@@ -0,0 +1,46 @@
+Bug#: 81727
+Product: Mono: Runtime
+Version: 1.2
+OS: All
+OS Details: 
+Status: NEW   
+Priority: Normal
+Component: misc
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: jonathan.gagnon at croesus.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+Summary: Semaphore.Close does not free the OS handle
+Please fill in this template when reporting a bug, unless you know what 
+you are doing.
+Description of Problem:
+When calling the Semaphore.Close method, the underlying OS handle is not 
+Steps to reproduce the problem:
+See attached example.
+Actual Results:
+Handle not freed.
+Expected Results:
+Handle should be freed.
+How often does this happen? 
+Every time.
+Additional Information:
+The Semaphore class uses the WaitHandle.Handle property, which is 
+obsolete in 2.0.  That property creates a SafeWaitHandle passing false 
+for the owner argument, meaning that it won't free the handle.

More information about the mono-bugs mailing list