Sending a message then closing program does not flush message.

So, calling NetClient.Disconnect("Message"); and then closing the application by exiting the Main function does not seem to send the disconnect message to the server and instead the connection closes by timing out.

NetClient.FlushSendQueue() does not seem to do anything just after Disconnect either.

My workaround was

while ((Peer as NetClient)?.ServerConnection != null)
        Thread.Sleep(10);

[RevoluPowered]

Found out the source of the issue, so what’s happening is, NetServer’s socket is getting cleaned up properly the first time it closes down / kind-of, then the NetClient properly disconnects.

If that same client reconnects to the server, even a new instance of it, the socket doesn’t close. When the server closes for the second time, the client has to timeout.

I think the issue is in the NetClient, and I’ll see if i can fix it for tomorrrow.

note it also doesn’t seem to be happening all of the time.

[sbarisic]

Lidgren_Test.zip

Here’s the result and the whole project. Tested with start NetTest.exe --server && start cmd /C "NetTest.exe && pause"