client thread issues

[GoogleCodeExporter]

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

Please use labels and text to provide additional information.

I believe client threads/instances aren't being properly cleaned up.  I see
two side affects related to this:

Sometimes when you go to restart to choose another character, you get
booted once you choose because 'you are already logged in'.

If the user count on the server is close to its limit (4-5 or so), and you
'restart' a lot, eventually the server will lock you out saying the server
is full, when it is not.

Original issue reported on code.google.com by ret...@gmail.com on 5 Feb 2009 at 9:09

[GoogleCodeExporter]

this may be the low level cause of a few issues including: performance issues,
possibly the mp bug (may have to do with reaching the system limit on threads 
and/or
contribute to the thread lock condition causing the bug), etc

easily reproducable.  click restart, then cancel.  Even though you are then
disconnected, your client thread is staying alive.  You can see this by going to
login, it will boot you once with the error in the log "Already logged in". 
(you wont
see anything client side other than a dc on your first login attempt)

There are probably other conditions that allow the client threads to stay alive 
even
with the player disconnected, which over time is probably resulting in a ton of
active (or sleeping) threads that shouldn't be there at all.  The above is a
reproducable one that I know of though that could maybe be used to find/test a 
fix

Original comment by ret...@gmail.com on 3 Mar 2009 at 6:43

[GoogleCodeExporter]

may have a fix.  currently testing on lineagedc's live server

Original comment by ret...@gmail.com on 4 Mar 2009 at 6:24

[GoogleCodeExporter]

Original comment by ret...@gmail.com on 4 Mar 2009 at 6:46

• Changed state: Invalid