windows doesn't like when messages are sent and nobody reads them
it seems to punish innocent sockets that listened on completly unrelated
ports. Since it resets the connections, we just ignore the message in
this situation, and try reading again. This seems to fix the issue.
windows doesn't like when messages are sent and nobody reads them it seems to punish innocent sockets that listened on completly unrelated ports. Since it resets the connections, we just ignore the message in this situation, and try reading again. This seems to fix the issue.
@Heideachim this should fix your issue.