Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m working on 2 Windows Services that have a common database which I want to lock (cross-process) with a system Mutex.
Now I’m wondering whether it’s ok to just call WaitOne() and ReleaseMutex() in a try-finally block or should I also dispose the Mutex (e.g. in a using block). If so I guess I should always catch the AbandonedMutexException on the WaitOne() method or am I wrong here?
A mutex is a Windows kernel object (here wrapped in a .NET object).
As such, it is an unmanaged resource that should be disposed.
More accurately, the .NET object contains a HANDLE to the mutex, which must be released/disposed of somehow.
I don’t trust that code sample in the Mutex class docs where the mutex object is not disposed. Although Henzi has a good point in comment: The Mutex object is static and would be either disposed by the finalizer or destroyed by the Windows kernel when the process exits.
Also, note that Close() disposes the object as well.
Of course, there’s nothing wrong with keeping an existing Mutex object in your app even while you don’t use it. They are light resources.