I have been getting this exception quite frequently lately:
I use the newest RunUO SVN with .NET Framework 4.0.
The error is related to this:
I am not an expert in locking mechanisms, so I am not sure where to go with this.
Maybe the wonderful devs of RunUO can look at this and fix it for those of us using .NET Framework 4.0 64bit on a blade server.
I use the newest RunUO SVN with .NET Framework 4.0.
Exception:
System.ArgumentNullException: Value cannot be null.
at System.Threading.Monitor.Enter(Object obj)
at Server.Network.NetState.Receive_Process(SocketAsyncEventArgs e)
at Server.Network.NetState.Receive_Completion(Object sender, SocketAsyncEventArgs e)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.Sockets.SocketAsyncEventArgs.FinishOperationSuccess(SocketError socketError, Int32 bytesTransferred, SocketFlags flags)
at System.Net.Sockets.SocketAsyncEventArgs.CompletionPortCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped)
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)
The error is related to this:
Code:
lock ( m_AsyncLock ) {
m_AsyncState &= ~AsyncState.Pending;
}
I am not an expert in locking mechanisms, so I am not sure where to go with this.
Maybe the wonderful devs of RunUO can look at this and fix it for those of us using .NET Framework 4.0 64bit on a blade server.