Client Performance after Multiple :lo

[kobnach]

I frequently leave my client running, doing :lo and then relogging, sometimes as a different character. When I do this often enough, the game will become unplayably sluggish after one more login - often with the same character as the previous one. I suspect a resource leak.

I mention the changes of character - different accounts too - in case the resource leak is there, rather than in the log out/relogin sequence. (I.e. clicking "forget me" might be the problem.)

Note by the way that "remember me" and "forget me" behave really strangely if one has multiple copies of the client open on the same comp., as I usually do. If two chars log out within about 5 min. of each other, both clients "remember" the same one.

[Jackard]

hmm thats interesting, i :lo several times so ill have to keep an eye on it

[PhaedrothSP]

The same thing happens to me, but it gets extremely laggy after I do it twice, that is :lo and log back in.
Though I usually log back in through the same account and character.

[Jackard]

Note by the way that "remember me" and "forget me" behave really strangely if one has multiple copies of the client open on the same comp., as I usually do. If two chars log out within about 5 min. of each other, both clients "remember" the same one.

it remembers whatever account you last logged in as. that seems natural enough to me

[kobnach]

it remembers whatever account you last logged in as. that seems normal enough.

Except it doesn't. If I have multiple client windows, it should remember which account last logged in with that window. As far as I know, each runs a separate instance of the client, so why do they get their memory confused?

[Jackard]

Are you pressing the Play button? I don't use the default client anymore, so maybe something is up with that.

[loftar]

Except it doesn't. If I have multiple client windows, it should remember which account last logged in with that window. As far as I know, each runs a separate instance of the client, so why do they get their memory confused?

That's probably because the client never stores that information in memory, but rather in Java's preference system. It could be argued that that should be changed, of course, but at least it's the reason why it behaves the way you observe.

The resource leak seems like a worse problem, though I haven't managed to trigger it myself, even though I often leave a client open for many consecutive sessions. If you don't want to wait for me to be able to trigger it, maybe you could try to get a heap dump of the client when it is in that condition and send it to me? Getting the dump is easy provided you have the JDK installed -- just run "jmap -dump:file=heap.dump PID" (where PID is the actual PID of the Java process), but sending it might be harder, since the generated file will be a couple of hundred MBs.

[Laremere]

This is very easy to trigger, just log in and out many times. I've been getting this as I've been teleporting from my hearth in the middle of a forest to RoB to build my wooden things in Brodgar. It is a client slow down, as in a cabin the game runs fine, but as soon as you take a step out-side the fps slows way down.

[kobnach]

The resource leak seems like a worse problem, though I haven't managed to trigger it myself, even though I often leave a client open for many consecutive sessions. If you don't want to wait for me to be able to trigger it, maybe you could try to get a heap dump of the client when it is in that condition and send it to me? Getting the dump is easy provided you have the JDK installed -- just run "jmap -dump:file=heap.dump PID" (where PID is the actual PID of the Java process), but sending it might be harder, since the generated file will be a couple of hundred MBs.

If I can get a dump, I'll do something like make it ftp'able from my site, and let you deal with the transmission problem. (It will be painful, I'm on DSL - assymetric consumer DSL.)

I may not be able to get it, however. I can't get your program to run on linux - where I have the JDK. I think the JDK is also available for various flavours of Winblows - but some experimentation will be required.

[kaka]

I can do that for you.
I'm having the same problem and, as you know, I can easily give you the dump.