Autologin session hang problem

[mistahmikey]

For a long time now, I have had a problem with sessions launched by autologin hanging. The problem only seems to occur when I try to log in new sessions - that is, when I initially use autologin to log in, say, six sessions on a computer, they all start up fine. But if I subsequently try to start another - and it doesn't matter if I log out one of the original ones out first, or just start up a 7th without logging one out - 9/10 times that session will hang after it launches the eq2 process. The hung session just sits there with a black background and a white square in the middle, and the everquest 2 version information is in the title bar. I have to use the task manager to kill it (and its status is "not responding"). If I subsequently launch eq2 using the SoE loader, the game launches without hanging.

This problem exists on different computers, and it persists across updates of eq2, graphics drivers, isxeq2, etc, all of which are the latest and greatest. I am running windows 7 ulitimate and NVidia graphics cards. And the computers are all massively overbuilt to run multiple game sessions, so I am confident there are no physical resource limitations.

In any case, I was wondering if anyone else has experienced this, and if so, are there any workarounds to avoid it.

Thanks.

 

[Kannkor]

For a long time now, I have had a problem with sessions launched by autologin hanging. The problem only seems to occur when I try to log in new sessions - that is, when I initially use autologin to log in, say, six sessions on a computer, they all start up fine. But if I subsequently try to start another - and it doesn't matter if I log out one of the original ones out first, or just start up a 7th without logging one out - 9/10 times that session will hang after it launches the eq2 process. The hung session just sits there with a black background and a white square in the middle, and the everquest 2 version information is in the title bar. I have to use the task manager to kill it (and its status is "not responding"). If I subsequently launch eq2 using the SoE loader, the game launches without hanging.

This problem exists on different computers, and it persists across updates of eq2, graphics drivers, isxeq2, etc, all of which are the latest and greatest. I am running windows 7 ulitimate and NVidia graphics cards. And the computers are all massively overbuilt to run multiple game sessions, so I am confident there are no physical resource limitations.

In any case, I was wondering if anyone else has experienced this, and if so, are there any workarounds to avoid it.

Thanks.

I'm confident to say this is unrelated to Ogre.

Do you use isboxer?

 

[mistahmikey]

I'm confident to say this is unrelated to Ogre.

Do you use isboxer?

I do not. On both of my computers, I only use innerspace, isxeq2, and ogre. I have set up affinity mapping using ogre proc, though. Wonder if that could somehow affect the process launch process?

 

[Kannkor]

I do not. On both of my computers, I only use innerspace, isxeq2, and ogre. I have set up affinity mapping using ogre proc, though. Wonder if that could somehow affect the process launch process?

I highly doubt it, because ogre proc doesn't get activated until AFTER you see the green "ISXOgre enabled." message. And if it's freezing before it finishes loading, it's not even getting to loading the extension at all, let alone finish loading it.

My best guess is there's some odd quirk with how innerspace loads eq2 that can have this random issue. I know I've had it happen before, but it is extremely rare for me, and I can't think of having a single one in months. But I have a friend who has it happen much more frequently. The problem is, it's nearly impossible to ask lax to look into it, because can't figure out how to reproduce it.

 

[Scoops]

I actually see this quite a bit, though it's not easily reproduced (until it happens, then it happens every time). Most of the time I see it when there are already adventure sessions active (already fighting in a zone), and you try to log in another character. I also have to kill it in task manager (the one that is using ~55M memory) and try again.

As a side note, sometimes I experience issues launching the first session -- there is a delay of probably 20-25 seconds. I discovered there's a process called "wws_crashreport_uploader.exe" blocking the launch. When I kill it, everything works as expected. I wonder if it's related?

 

[Kannkor]

As a side note, sometimes I experience issues launching the first session -- there is a delay of probably 20-25 seconds. I discovered there's a process called "wws_crashreport_uploader.exe" blocking the launch. When I kill it, everything works as expected.

Fantastic find.

In my latest patch:
If ISXOgre is set to remove the awesomiun thingy, it will now also remove "wws_crashreport_uploader.exe" since it CAUSES FUCKING 20-40 SECOND DELAYS IN LOADING THE FUCKING GAME. Thanks to "Scoops" for finding this.