WoWs crashing on exit in pwnboxer

[GatorKram]

Every now and then, when I finish playing wow, and I use the button in pwnboxer to kill off my wows, the wows will crash.

What is even more odd, is I see other wow.exe processes still running, and I
have to kill them myself.

[Heartspark]

Thats normal, not sure exact reason but happens all the time with wow does not effect anything.

The other processes will disappear after a minute.

[Ualaa]

Used to happen with IS Boxer.
If we were to broadcast exit, either Alt F4, exit now (click), or escape x2 from the character screen.

Not really sure what Lax did, but he removed it in a recent build.

Was not a problem really.
Just an inconvenience.
You're not hurting your warcraft install any.
But you can manually close them one at a time, if you don't want the error.

[Poyzon]

Well, the harm in getting the error is that some addons may lose any customization that you did during your session.

I usually get this error if I share a single WoW folder across multiple game instances. I get around it by just logging out each screen manually and waiting for each one to finish closing before moving to the next.

[TheMuffinMan]

Originally Posted by Poyzon

Well, the harm in getting the error is that some addons may lose any customization that you did during your session.

I usually get this error if I share a single WoW folder across multiple game instances. I get around it by just logging out each screen manually and waiting for each one to finish closing before moving to the next.

Ya I never use the "close all winwdows" for this very reason.

[Nghtmr9999]

Originally Posted by TheMuffinMan

Ya I never use the "close all winwdows" for this very reason.

Same. Granted it is only two windows for me, but still

[Heartspark]

I never had any problem with add-ons getting messed up because of that.

[TheMuffinMan]

Originally Posted by Heartspark

I never had any problem with add-ons getting messed up because of that.

Not a 100% thing... I had spent an hour setting up a new team... and that happened and I lost everything.

I was a sad panda =(

[Ualaa]

If you camp out, addons generally save their settings.

If you just Alt + F4 out, or hit the X in the upper corner (playing windowed mode), they never retain changes. That goes for macros which are being saved server side too.

If wow crashes during the logging out, you've got an increased chance of being in the second category instead of the first.

[Tim]

The issue is actually systemic to World of Warcraft being ran multiple times. The game client itself wasn't designed to be ran multiple times on 1 system. What is actually occuring is this: Upon wow.exe exit, a few configuration files are written to by the game client. Depending on how fast your PC is, these files could take 1/10th of a second, or 5 seconds, to write and exit. The problem is that the WoW client takes specific control of a few key files (config.wtf, macro cache, item cache, etc), and if 2 instances of WoW.exe closing at the same time, on a fast machine, occur in a way where the first has control over those specific files while the 2nd is attempting control, will result in a wow.exe error.

The error doesn't cause any issues, nothing gets corrupted, no game issues requiring a fix. Just click OK and continue on your merry life

Note: This doesn't happen often, but if my PC is going especially fast, it may occur.

Note #2: I'm considering adding something to Pwnboxer to SLOW DOWN how WoW exits itself, making it not step on top of another WoW's foot. Not many people have had issues so it took the backburning.

TLDR? The crashing is due to multiple WoW's writing the same files upon exit, but nothing really happens, so there is no issue