According to the documentation:
"a
SemaphoreSlim
doesn't use a Windows kernel semaphore".
Are there any special resources used by the SemaphoreSlim
which make it important to call Dispose
when the SemaphoreSlim
will no longer be used?
If you access the AvailableWaitHandle
property, then Yes, you must call Dispose()
to cleanup unmanaged resources.
If you do not access AvailableWaitHandle
, then No, calling Dispose()
won't do anything important.
SemaphoreSlim
will create a ManualResetEvent
on demand if you access the AvailableWaitHandle
. This may be useful, for example if you need to wait on multiple handles. If you do access the AvailableWaitHandle
property, and then fail to call Dispose()
you will have a leaked ManualResetEvent
, which presumably wraps a handle to an unmanaged CreateEvent
resource that needs a corresponding call to CloseHandle
to clean up.
As other posters have pointed out, you should call Dispose()
when you are done with any object that implements IDisposable
. In this case, there are several risks to ignoring that practice, even though it may technically be safe to do so:
SemaphoreSlim
to where Dispose()
is required.SemaphoreSlim
is exposed outside of your class, calling code might reference the AvailableWaitHandle
property not realizing that your class isn't disposing the SemaphoreSlim
and create an unmanaged resource leak.Yes.
It may use a ManualResetEvent
that uses a SafeWaitHandle
which is a SafeHandle
and it has an unmanaged handle.
You can see it in the reference source here.
SafeHandle
is finalizable so if you don't dispose of it (by disposing of the SemaphoreSlim
) it will go to the finalizer that will need to do that for you. Since the finalizer is a single thread it may get overworked in certain situations so it's always advisable to dispose finalizable objects.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With