Probally caused by lag and not sure anything can be done about that.

When programs send data over network they use 'sockets' to do so. There are two kind of sockets:
a) blocking - the program pauses/hangs until the operation is completed. For example when wanting to recieve data, the program will not continue with its other tasks until data has been recieved.
b) nonblocking - the program does not pause while doing the socket thing. Instead data is put into a buffer and when the program wants to recieve data, it takes data from the buffer. But what if buffer is empty, for example because connection was lagging? Then the socket would have to wait ("block") again, and informs about that with message: "would block." The program can then retry later, when connection is hopefully better.