Thread hanging on Client.dispose()/ Client.close()

[doriancransac]

I noticed this issue over at EsotericSoftware /
kryonet : EsotericSoftware#142

and remembered that I spent quite a bit of time a few months ago trying to diagnose this, unsuccessfully. I'm curious if that's something that could be addressed on this forked repo in light of some of the info that was posted recently?

[crykn]

I'm not using KryoNet much at the moment, but the most common suggestion seems to be to roll back EsotericSoftware@a7e9661 (see here, here and here). If it is confirmed that that works (on all platforms), it is a rather trivial change. Then we'd just need to figure out if this causes any other issues, in particular regarding EsotericSoftware#93, which was supposed to be fixed by the aforementioned commit.

[doriancransac]

Hey, I totally understand, thanks for the quick feedback.

I'm personally not in a huge hurry to fix this so I won't try and patch it myself (I don't really have enough understanding of kryo to run proper regression tests anyways to submit a proper PR) but I thought it could make sense to at least mention this in case someone would be interested in testing & add the fix at some point.