Interact With Target and ISBoxer Crashing in WoW

[Lax]

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.

.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.

[Brett-Blackrock]

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.

[Ñightsham]

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.

[rootz]

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.

[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
Assist_delay.jpg

.. 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.

[rootz]

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
Assist_delay.jpg

.. 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

[Mickthathick]

@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.