I think I can cast the blame of this bug on the server's failure to close the connection completely when a client sends the Disconnect message. We've also had to put a sh*tton of error correction throughout the server's binary because of issues we found when just ATTEMPTING the disconnect. Any of that error handling could have caused problems with the bitstream or otherwise. Triaged.
I think I can cast the blame of this bug on the server's failure to close the connection completely when a client sends the Disconnect message. We've also had to put a sh*tton of error correction throughout the server's binary because of issues we found when just ATTEMPTING the disconnect. Any of that error handling could have caused problems with the bitstream or otherwise. Triaged.