Greetings, spiral knights community. This is my first post here in the forums (I'm a shy one), and it's about something that's been troubling me since I started playing. I play on a fairly weak laptop: I somewhat lag when more people and more visual effects are on screen, and I take longer to load than most other party members. That is not a problem, and I've grown used to it. My problem is, whenever I play Spiral Knights for a while (usually at least 1 or 2 hours), my game ends up crashing. Well, I guess "crashing" isn't the right term. It freezes. If I try calling the task manager to kill Java.exe, the process will behave like a zombie process (won't let itself be killed and won't disappear), which forces me to logoff everytime this happens. This is borderline annoying to me, but I've grown used to the quirks of having a bad computer, and usually I could log off fast enough and come back in time to not be ejected from my current dungeon, or at least, come back to the game. But lately, not even that has been allowed to me: everytime I try coming back after such thing happens, the game prevents me from returning, just freezing on login (at least I can kill java.exe...). Trying to login, kill java.exe and trying again doesn't seem to help matters; I have to stay around 15-30mins without trying to login to be able to return to the game (not sure of exact time). I've been having this "zombie java" problem since I started playing (January, even though I took a LOOOOOOOONG break till around the end of july, where I started a new character) and I'd like to know possible solutions, or if someone else has this problem.
I apologize for the wall of text. Any requests about more info, let me know on the replies (and preferentially provide the steps to get that info :P ). If I had to guess by myself, I'd say Spiral Knights has some memory leak (since my game only gets like that after an hour or two of playing), but either way, any help will be appreciated :)
Small bump, just wanted to add that, since disabling steam overlay, the problem has been occurring less often (but still occurs...)