I think I might have found a lead on the zombie lobby issue. I had a jnet tab left open, and then I refreshed my dhcp session via
ipconfig /release && ipconfig /renew
due to my vpn getting into a bad state, and I think I might have gotten a different ip address afterwards.
Just running the command again doesn't seem to cause the issue, but I think I'd only get a new ip address a fraction of the time.
One possibility might be that the socket library doesn't handle the client ip changing and gets into a weird state. That matches the behavior where data up to the server seems to still work. You can still send chat / create lobbies, but the data over the socket back to the client never seems to make it to the, so the client never sees the lobby they have created until a refresh.
I think I might have found a lead on the zombie lobby issue. I had a jnet tab left open, and then I refreshed my dhcp session via
ipconfig /release && ipconfig /renew
due to my vpn getting into a bad state, and I think I might have gotten a different ip address afterwards.Just running the command again doesn't seem to cause the issue, but I think I'd only get a new ip address a fraction of the time.
One possibility might be that the socket library doesn't handle the client ip changing and gets into a weird state. That matches the behavior where data up to the server seems to still work. You can still send chat / create lobbies, but the data over the socket back to the client never seems to make it to the, so the client never sees the lobby they have created until a refresh.