kerryjiang / WebSocket4Net

A popular .NET WebSocket Client
752 stars 272 forks source link

Unhandled NullReferenceException (FireMessageReceived) #143

Open 80dB opened 5 years ago

80dB commented 5 years ago

Version: WebSocket4Net v0.15.2 OS: Windows Server 2016

Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.NullReferenceException at WebSocket4Net.WebSocket.FireMessageReceived(System.String) at WebSocket4Net.WebSocket.OnDataReceived(Byte[], Int32, Int32) at SuperSocket.ClientEngine.AuthenticatedStreamTcpSession.OnDataRead(System.IAsyncResult) at System.Net.LazyAsyncResult.Complete(IntPtr) at System.Net.LazyAsyncResult.ProtectedInvokeCallback(System.Object, IntPtr) at System.Net.Security._SslStream.ProcessFrameBody(Int32, Byte[], Int32, Int32, System.Net.AsyncProtocolRequest) at System.Net.Security._SslStream.ReadFrameCallback(System.Net.AsyncProtocolRequest) at System.Net.AsyncProtocolRequest.CompleteRequest(Int32) at System.Net.FixedSizeReader.CheckCompletionBeforeNextRead(Int32) at System.Net.FixedSizeReader.ReadCallback(System.IAsyncResult) at System.Net.LazyAsyncResult.Complete(IntPtr) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at System.Net.ContextAwareResult.Complete(IntPtr) at System.Net.LazyAsyncResult.ProtectedInvokeCallback(System.Object, IntPtr) at System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32, UInt32, System.Threading.NativeOverlapped*) at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)

And before you ask, no idea when/what/how it happend, I was sleeping :)