Factorio Forums

The client will hang (as in sit an wait, not doing anything) after a connection to the server is established (that is, once a ConnectionAccept message has been received). If no heartbeat messages or transferblock messages are sent, the client will sit and wait for information from the server indefinitely. There is no way to get it to respond, requiring the game to be closed.

Thanks for the report,

Can you provide some more specific information about the issue?

What sort of set up are you using to create this situation, and how can we reproduce it?
Can you provide a factorio log file?
https://wiki.factorio.com/index.php?tit ... _directory

That would help a great deal

I wrote my own program to act as the server (was easier than writing a program to drop packets). Would you like me to post my code for that? I haven't copied an pasted anything from Factorio's source code but it contains details on how your network protocol works and how the game in general works.

To be clear, this is not an issue with your server program - this is the client not properly handling a connection to the server. The server should never be in this condition (unless it was powered off/disconnected from the internet at just the right moment. However, the client should be checking to make sure the server is still alive. '

The log is available here:
http://pastebin.com/6d0mrxgh

Forgot to upload the log after I close it, but not much else happens:

538.834 Info MultiplayerManager.cpp:913: networkTick(15695) mapTick(-1) changing state from(VerifyingConnection) to(QuitScheduled)
538.837 Info MultiplayerManager.cpp:161: NetworkTick(15695) quitting multiplayer connection.
538.839 Info MultiplayerManager.cpp:913: networkTick(15695) mapTick(-1) changing state from(QuitScheduled) to(Disconnected)
538.933 Info Router.cpp:509: Router peerID(0) shutting down.
538.934 Info WindowsUDPSocket.cpp:160: Socket closed
538.934 Info Router.cpp:536: Router state -> Disconnected
543.262 Goodbye

If I got it right. In some specific state, the client doesn't timeout the server but just waits for ever if he doesn't get the packet it waits for.

Yep, thats exactly it.

All problems of this kind have been fixed If I remember it correctly, let me know if it isn't the case.