Zombie wow.exe processes

[heyaz]

I've had the issue with Innerspace not fully launching a group - 1 or 2 clients will sometimes never be loaded.

In the second to latest version (I haven't upgraded to newest just yet), it is now extremely common.

- Restarting Innerspace seems to fix the issue
- I discovered the Wow.exe processes DO always get loaded - they just never appear in your screen and end up a zombie process in the background sucking up tons of CPU and memory.
- I have to kill the orphaned processes manually before start innerspace again or I could end up running 10 wow clients when I'm just trying to 4 box.

Some details about my setup:
Machine (in brief): Q6600, 8GB Ram, ATI 4890 1GB GDDR5, Intel X25-V SSD.

Windows: Dual monitor, 1440x900 resolution on both. Font sizes are about 130%, and I'm under the impression that can cause stacked windows during loading (which is easy to fix by pip switching, not worried about it).

[Lax]

What version of Windows is this on?

And you're saying this is with the Development build of IS? or were you saying the 2nd to latest version of ISBoxer?

I haven't heard of anyone having zombie WoW processes with IS, but if you're not on the development build try switching to that and see if it helps (right click IS, select Patcher, check "Download development (test) patches", restart IS. can switch back at any time the same way). If that doesn't help, probably have to start shutting down other running programs to see if maybe one is interfering somehow.

[mrmcgee21]

I'm running win7 and innerspace and having the same issue. What's happening is when you close your entire team at once ( via exit game ) sometimes they dont fully close or something and your left with an extra wow.exe under processes on the task manager ( usually its only taking up about 50mb ). So then when you go to load the next time it skips over that window in the loading process until you go manually end it in the task manager, its a new issue for me ( never had the problem in bld 33 ).

[Lax]

Okay. If you close all your guys at once, usually WoW will just crash on you and it pops up the standard WoW error box :P

I'll have to figure out how to get it to be a zombie instead, I guess.

[Zappy]

That doesn't seem specific to IS Boxer, as I'm running keyclone and get one of the instances to crash when exiting at the same time at least 50% of the time. The problem is that when it crashes, the process never ends, so now i'm used to whenever seeing one crash to kill the process before relaunching.

[heyaz]

I'm running the latest release, not a development version.

It must be because I usually close them all at once via /exit. It usually loads up 2-3 wow errors. I'm not sure if it ends up creating the zombies as well. I'll try NOT exiting like that and see if it fixes the issue.

[Noids]

I get a similar problem occasionally and also do the bulk exit, will try the single box exit and see if that resolves it.

[deadguyfred]

About 30% of the time when I log off one of my MB teams (Im using ISBoxer and use mouse broadcast to log them all off at once), I will need to open the windows taskmanager and "end process" on one or more wow.exes to totally close out wow. This started after patch 3.3. I use windows Vista sp2

[Multibocks]

Hilarious but this is my fix to make sure all windows load when I start MBing. I have to mouse over my windows task bar when I start loading the team. If I dont I guarantee you it will stop loading at one window. Very strange, but it works. This is from a fresh pc start up so I know there are no zombie wows running in the background, but I have seen that too. I also close one window at a time to ensure I dont get the wow crash error.

[Lax]

The crash on exit is fixed as of an unannounced WoW 3.3.2 fix.

Let me know if the zombie issue you guys were experiencing continues.