Fixed nullref exception after stopping the KcpServer #47
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After calling KcpServer.Stop() method it destroys underlying socket, but don't clear the connections list. At the next Tick those connections tries to send a "Disconnect" message and throws exceptions because socket doesn't exist anymore.
Moreover, if you start the server again - those connections remain in the list and will spam errors trying to Disconnect themselves and failing due to wrong socket binding.
In short. We need to clear existing connections when stoppping the server.