This is due to EventWaitHandles already being destroyed, and mre.Set() being called in a finally block -- it leads to unhandled ObjectDisposedException that kills the host application (IIS pool in our case). Encasing mre.Set() with try/catch(ObjectDisposedException) block in async callbacks (MultiGet, Stats, maybe in other places) should alleviate this problem.
I have the same issue.
We have the same issue. As the following code fragment in 'PerformMultiGet' executes on a ThreadPool thread, there is no way for an application to recover from this.
An edited crash report :
System.ObjectDisposedException was unhandled
Message="Safe handle has been closed"
at Microsoft.Win32.Win32Native.SetEvent(SafeWaitHandle handle)
at Enyim.Caching.MemcachedClient.<>c__DisplayClass14`1.b__11(IAsyncResult iar)
I have the same issue. too
We are going to fix this on the Couchbase fork of this project: http://www.couchbase.com/issues/browse/NCBC-198