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 [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=76983 --- shadow/76983 2005-12-13 12:50:59.000000000 -0500 +++ shadow/76983.tmp.1301 2005-12-13 12:50:59.000000000 -0500 @@ -0,0 +1,65 @@ +Bug#: 76983 +Product: Mono: Class Libraries +Version: 1.0 +OS: +OS Details: GNU/Linux +Status: NEW +Resolution: +Severity: +Priority: Major +Component: CORLIB +AssignedTo: [EMAIL PROTECTED] +ReportedBy: [EMAIL PROTECTED] +QAContact: [EMAIL PROTECTED] +TargetMilestone: --- +URL: +Cc: +Summary: System.Threading.Mutex stays locked when process exits + +Description of Problem: + +When I create a locked System.Threading.Mutex object and don't explicitely +call Mutex.ReleaseMutex() or if mono gets killed then the mutex will stay +locked forever (until I manually remove all files from $HOME/.wapi). + + +Steps to reproduce the problem: + +using System; +using System.Threading; +using System.IO; + +public class T { + public static void Main(string[] args) { + bool gotLock; + Mutex m = new Mutex(true, "mymutex", out gotLock); + Console.WriteLine("Acquired Lock: " + gotLock); + } +} + +Actual Results: + [EMAIL PROTECTED] ~/t > mcs t.cs [EMAIL PROTECTED] ~/t > ./t.exe +Acquired Lock: True [EMAIL PROTECTED] ~/t > ./t.exe +Acquired Lock: False + +Expected Results: + +2 times an "Acquired Lock: True" message + +How often does this happen? + +Everytime + +Additional Information: + +I'm using gentoo linux on an x86 Pentium4 processor. + [EMAIL PROTECTED] ~/t > mono --version +Mono JIT compiler version 1.1.10, (C) 2002-2005 Novell, Inc and +Contributors. www.mono-project.com + TLS: __thread + GC: Included Boehm (with typed GC) + SIGSEGV : normal _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
