search

lnobad / lidgren-network-gen3

Automatically exported from code.google.com/p/lidgren-network-gen3
0 stars 0 forks source link

Disconnecting users from server induces timeout on other clients #88

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
(The ManyClients demo is suitable for testing this.)
1. Setup NetServer
2. Connect in 100 NetClient's
3. Disconnect 20 of the NetClients

What is the expected output? What do you see instead?
80 Clients remaining connected, instead most or all of the clients will 
timeout; during the immediate moments from disconnecting 20 clients, to when 
they timeout and disconnect - packet delivery to the remaining 80 clients 
stutters then fails completely.

What version of the product are you using? On what operating system?
Zip from 4 days ago; Win 7; .NET3.5

Please provide any additional information below.

If I was to guess, when clients are deleted, some kind of clean-up process 
engages to clean out their packets from the queues - this process takes so long 
to execute that the other users sit 'waiting', and eventually hit a time-out 
and are also disconnected (adding extra work, and making the problem worse).

This problem is more severe the more clients you disconnect concurrently - 1-3 
doesn't seem to trigger a problem. Disconnect more however and suddenly it will 
cascade out further.

Original issue reported on code.google.com by a...@gwala.net on 15 Sep 2011 at 11:34

GoogleCodeExporter commented 9 years ago 
I can't seems to reproduce this. Do you disconnect in some other way that just 
closing the window? Disconnecting barely use any resources; shouldn't be a 
problem disconnecting a 1000 connections in a second or less.

Original comment by lidg...@gmail.com on 25 Sep 2011 at 9:27

GoogleCodeExporter commented 9 years ago 
I'll put together a reproduction for you (been travelling, apologies for the 
delayed response). It seems to appear more often if you have the connections 
actually doing something.

Original comment by a...@sinewavecompany.com on 23 Oct 2011 at 5:12

GoogleCodeExporter commented 9 years ago 
Revision 271 might have an impact on this issue; try it.

Original comment by lidg...@gmail.com on 6 Nov 2011 at 9:50

GoogleCodeExporter commented 9 years ago 
Will do, thanks.

Original comment by a...@sinewavecompany.com on 8 Nov 2011 at 8:58

GoogleCodeExporter commented 9 years ago 
Did revision 271 fix your problem?

Original comment by luisestr...@gmail.com on 30 Nov 2011 at 1:23

GoogleCodeExporter commented 9 years ago 
Assumed fixed in 271

Original comment by lidg...@gmail.com on 26 May 2012 at 8:27