Interact With Target and ISBoxer Crashing in WoW

I have a new install of ISBoxer and I configured the Interact With Target key and have it working properly. The slave screen (only 2 boxing to start) will engage combat / pick up quest / etc and close to melee distance like I want. However it causes the game client (WOW) to crash fairly often (5-15 minutes). I've tried binding the action to a mouse button, a keystroke through my mouse button, a keystroke on the keyboard all different things and it still causes the crash. I've tried testing it in various situations (combat, casting, moving, picking up quests) and it seems crash in all situations for no reason. Here is my setup:

http://www.privatepaste.com/6c7edf5c05

I've also posted on the ISBoxer forums and asked around in a few IRC chats. I don't think I've set the keys up into being a loop because it crashes with every different key binding I collect but it doesn't crash every time I click it. Any help would be greatly appreciated.

-Brett

Everything looks okay at a quick glance. I think you're going to have to paste the crash report.

I changed one thing after following the video tutorial but I'm still getting the same crashes.

Here is the crash log:

http://www.privatepaste.com/491dc63491

and here is my new setup when that crash occurred:

http://www.privatepaste.com/752335208c

I removed Interact With Target from Variable Keybindings and I manually set the actions to broadcast all per the instruction in your video. However crash is still occurring. (Although it seemed to last longer before a crash)

I'm sorry I guess I changed two things. :D

I'm terrible at reading crash reports, but if your video settings are too high I would try turning them down to see if the crash still occurs. Also, try using DX9 rather than DX11.

I have been having a very similar issue with IRT, but only with 1 account (always the same account) crashing and only on some characters when player in ISboxer mode.

e.g. I play on my pally on account A and can IRT with no issues, but if I play on my warlock or rogue on account A as soon as I IRT the account A window crashes.

Dropped the graphics settings and restarted in DX9. Was hopeful for about 15 minutes then crashed. I'm trying not to spam it, trying to be very careful.

It's like being given a beautiful girl's number then losing it on the way home from the bar. I've multi-boxed manually since before BC came out. Alt tabbing between the two and doing double of all the gather quests and turning things in etc. That was until I saw a guy running around Shattrath with 10 shamans and he told me about ISBoxer and dual-boxing.com. Then I looked this up and couldn't be more excited. I just can't get it to work :( So close!

Well, I can't say that I've ever heard of this problem before. I'm guessing you'll have to wait for Lax to look at the crash report.

This looks like a completely legitimate (as in, unrelated to Inner Space or ISBoxer) WoW crash. The stack in the current thread is 100% wow.exe, with no Inner Space stuff in it. That's usually (but not 100%) a good indicator that the problem code in question is entirely within WoW, and providing this crash log to the right WoW developer should result in a bug fix. Or at least a narrow area for them to look at.

I'll take a closer look shortly and see if I can come up with something that might help, but that's my initial impression.

Cool, thank you very much for your help it is much appreciated. Let me know. It just happened again. I thought maybe the other mods I was using was causing it, I've shut them all off along with turning down my graphics and reverting to DX9. I've never had the problem before, but I've also never used the interact with target function before.

The crash report of course confirms that it is crashing during the time that WoW is processing its InteractUnit Lua function. The only other thing that I can say about it is to more forcefully say, this definitely appears to be a bug in WoW.

The following will mean absolutely nothing to you, but here's the crash.

Code:

---

.text:00977614                mov    eax, [esi+0BCh]
.text:0097761A                mov    ecx, [eax+20h]  ; crashing here because eax is 0
.text:0097761D                mov    edx, [ecx]
.text:0097761F                mov    eax, [edx+30h]
.text:00977622                call    eax

---

I don't hack the WoW client these days so it also means next to nothing to me. But, a WoW client developer could use his debugger and see the line of code that corresponds to, and see something like ... this->memberA->memberB->SomeMethod(), and the problem in your case is that memberA does not hold an object. His job would then be to prevent this crash from occurring when the object does not exist. I don't know what conditions make the object not exist (or, therefore, what you should be doing differently).

That's about as far as I can help on this, you should provide them your crash log and feel free to paste that or point them at my analysis.

I don't know much about coding but next time in crashes I will include an analysis along with the crash report. Again thank you very much for you help. I greatly appreciate it.

This sort of thing was happening to me as well, but only when playing a single character, it has yet to happen when playing 5 characters via ISBoxer.

Next crash I'll send to Blizzard.

I have the same crash on my main client now. For 36 levels with 5 clients i had no problems and now it crashes every time just from today. There not been a wow update for a while and this has been working fine until today. Technically nothing changed and rebooting machine makes no difference. Trying the replicate the crash without isboxer but after 1/2 a hour doing IWT nothing crashed. Soon as load back my set it's start all over again.

Nothing updated in isboxer Lax?

edit: It only crashes when you do not select a target to interact with. Simple said if you select a target and hit your keybinding it won't crash but as soon as you have nothing selected and you hit the keybinding it will crash. This is a new thing to me.

If it crashes when you try to IWT but have no target, that would definitely be a WoW bug to report, and it would explain to me why people would get it intermittently with ISBoxer, but not typically without.

Here's why...

The inherent delay in /assist, as diagrammed here from http://isboxer.com/wiki/Game_features#Assist
Attachment 711

.. will increase the odds that your slave windows will randomly crash due to attempting to assist. You would get this crash intermittently on slaves when you select a mob and immediately press IWT. The longer you have your target before pressing IWT, the safer it would be.

Quote:

---

Originally Posted by Lax

If it crashes when you try to IWT but have no target, that would definitely be a WoW bug to report, and it would explain to me why people would get it intermittently with ISBoxer, but not typically without.

Here's why...

The inherent delay in /assist, as diagrammed here from http://isboxer.com/wiki/Game_features#Assist
Attachment 711

.. will increase the odds that your slave windows will randomly crash due to attempting to assist. You would get this crash intermittently on slaves when you select a mob and immediately press IWT. The longer you have your target before pressing IWT, the safer it would be.

---

It's my main crashing when i have nothing selected as far as i can replicate it. Not a big deal just more letting you know what happens in-case there was a change somewhere :)

@Lax @ rootz This is also when I get the crash occurring, when I either don't have anyone selected and I IWT or I have someone selected but I am out of range when I IWT.