search

ARLM-Keller / msnp-sharp

Automatically exported from code.google.com/p/msnp-sharp
0 stars 0 forks source link

NullReferenceException in TcpSocketMessageProcessor.Disconnect #320

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.Cannot reliable reproduce, probably a race condition
2.
3.

What is the expected output? What do you see instead?

What version of the product are you using? (MSNPSharp, OS, Mono etc.)
msnp-sharp-5.0.0.2717

DotNET = 4.0.30319.488
User = NT AUTHORITY\LOCAL SERVICE
ProcessorCount = 4
OperatingSystem = Microsoft Windows NT 6.1.7601 Service Pack 1 (64-bit)
Is64BitProcess = True
CurrentDirectory = C:\Windows\system32

Is your code clone from GIT or download from our download page?
Download from your site

Please provide any additional information below:
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
Stack:
   at MSNPSharp.Core.TcpSocketMessageProcessor.Disconnect()
   at MSNPSharp.NSMessageProcessor.Disconnect()
   at MSNPSharp.NSMessageHandler.OnSignedOff(MSNPSharp.SignedOffEventArgs)
   at MSNPSharp.NSMessageHandler.OnProcessorDisconnectCallback(System.Object, System.EventArgs)
   at System.EventHandler`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Invoke(System.Object, System.__Canon)
   at MSNPSharp.NSMessageProcessor.OnConnectionClosed(System.Object, System.EventArgs)
   at MSNPSharp.Core.SocketMessageProcessor.OnDisconnected()
   at MSNPSharp.Core.TcpSocketMessageProcessor.EndReceiveCallback(System.IAsyncResult)
   at System.Net.LazyAsyncResult.Complete(IntPtr)
   at System.Threading.ExecutionContext.runTryCode(System.Object)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode, CleanupCode, System.Object)
   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.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)
   at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped

Original issue reported on code.google.com by dutoit...@gmail.com on 7 Mar 2012 at 6:54

GoogleCodeExporter commented 8 years ago 
How can this happened? You have multiple thread calling disconnect()?

Original comment by freezing...@gmail.com on 7 Mar 2012 at 7:17

GoogleCodeExporter commented 8 years ago 
This issue was closed by revision e5f15caefc0c.

Original comment by freezing...@gmail.com on 7 Mar 2012 at 7:18

GoogleCodeExporter commented 8 years ago 
Please check out the latest master branch from our repo, thanks.

Original comment by freezing...@gmail.com on 7 Mar 2012 at 7:19

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
It seem you are using very very old version. We fixed this in v5.0.1. See 
revision 7b0a18f661b9

This is not a thread calling issue.

Original comment by hepha...@gmail.com on 7 Mar 2012 at 12:24

GoogleCodeExporter commented 8 years ago 
This issue was closed by revision c5c4fb7f51ee.

Original comment by hepha...@gmail.com on 7 Mar 2012 at 12:44

GoogleCodeExporter commented 8 years ago 
Duplicate of issue 313.

Original comment by hepha...@gmail.com on 7 Mar 2012 at 1:22