Windows specific crash bug where WSAECONNRESET can occur randomly with UDP sockets client/host

[silbinarywolf]

What's the issue?

I have both a server and client using UDP, both sending and receiving from each other.

When calling receive on a UDP socket where there's a random chance that it'll fail with an WSAECONNRESET error (currently not catchable as it's unreachable code).

A fix I know currently works:

• Updating recvfrom error handling to catch WSAECONNRESET like so:

.WSAECONNRESET => error.ConnectionResetByPeer,

• Catching that kind of error when calling sock.receive and ignoring it.

How various libraries avoid this issue:

• netcode.c, simply ignores the error and continues.
  • https://github.com/networkprotocol/netcode/blob/master/netcode.c#L843
• Golang, disables SIO_UDP_CONNRESET behaviour
  • https://github.com/golang/go/blob/master/src/internal/poll/fd_windows.go#L338
  • Original issue: net: UDPConn.ReadFrom failure on Windows golang/go#5834

Various other sources talking about this issue:

• https://stackoverflow.com/a/54315015/5013410
• https://stackoverflow.com/questions/38191968/c-sharp-udp-an-existing-connection-was-forcibly-closed-by-the-remote-host
• https://stackoverflow.com/a/15232187/5013410
• https://stackoverflow.com/a/6302916/5013410
• https://learn.microsoft.com/en-us/windows/win32/api/winsock/nf-winsock-recvfrom
  • WSAECONNRESET section says: "On a UDP-datagram socket this error indicates a previous send operation resulted in an ICMP Port Unreachable message."