NetGore

I'll look into it. My guess is just someone got accepted to log in twice somehow. It may be already handled, though, since that is just an assertion.

It just happened again, with the same account X_X Also, after the assertion there's a throw new argumentexception so it isn't really handled I guess

EDIT:

I managed to talk to the person and he said it started when he tried fullscreen. No idea if it has something to do with it, but might help you I guess. However, I tried fullscreening but didn't get any problems.

Just made a commit that will still raise assertions, but no exceptions and should be able to gracefully recover on this issue.

Thanks SVO is still a bunch of revisions behind though, so it might be a while before I can "test".

EDIT:

When I posted about the font crash I tried logging in again and now I have the same problem each time I try to log in. Apparently when the client crashes it doesn't dispose for quite some time.

So I found a cause for this (haven't updated to the latest fixes though).

Here's what I did:

1. Load 2 clients
2. Log in with Client A, select a character and log in
3. Log in with Client B but stay at char selection screen
4. Log back in with client A and log in with a character
5. Select a character to log in with on Client B

==> Server goes whining it's already there.

Client B should be back at the log in screen when Client a logs in.

Update:

What revision fixes this? I tried applying r4438 but I still got the assertions, I then commented them but other assertions popped up.