What's new
  • Visit Rebornbuddy
  • Visit Resources
  • Visit API Documentation
  • Visit Downloads
  • Visit Portal
  • Visit Panda Profiles
  • Visit LLamamMagic

WoW crashing with honorbuddy

FireFreak

Member
Joined
Jan 30, 2012
Messages
104
Reaction score
1
WoW just closes after some time Honorbuddy runs, since a few days, even in BG's, check the log it crashes at ~7:19.
It is some exception error, I'll try to make a screenshot the next time.
 

Attachments

Just found out it's the same as this, any fix?
http://www.thebuddyforum.com/honorbuddy-forum/support-issues/51104-honorbuddy-dcs-wow-errors.html

EDIT: I checked my logs and it seems like it always disconnects when Flightor tries to unstuck.

Just check this new log, it probably crashed at 7:37.

Code:
[07:37:36:067] [Gatherbuddy2]: Harvested Azsharas Schleier.
[07:37:36:186] Activity: Unterwegs zum n?chsten Hotspot
[07:37:36:356] Spell_C::CastSpell(75207, 0, 0x0, 0) [57]
[07:37:50:688] System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Exception: Process must have frozen or gotten out of sync; InjectionFinishedEvent was never fired.
   at BlueMagic.ExecutorRand.Execute()
   at Styx.WoWInternals.World.GameWorld.MassTraceLine(WorldLine[] lines, CGWorldFrameHitFlags[] flags, Boolean[]& hitResults, WoWPoint[]& hitPoints)
   at Styx.WoWInternals.World.GameWorld.MassTraceLine(WorldLine[] lines, CGWorldFrameHitFlags[] flags, Boolean[]& hitResults)
   at Styx.WoWInternals.World.GameWorld.MassTraceLine(WorldLine[] lines, CGWorldFrameHitFlags flag, Boolean[]& hitResults)
   at Styx.Logic.Targeting.DefaultTargetWeight(List`1 units)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Delegate.DynamicInvokeImpl(Object[] args)
   at System.Delegate.DynamicInvoke(Object[] args)
   at (Object , Object[] )
   at Styx.Logic.Targeting.#Dr(Delegate e, Object[] args)
[07:37:50:702] [Flightor]: Unstuck attempt 4

Goes on till attempt 6. Whatever, check it out yourself.
 

Attachments

Last edited:
make a new Hb installation from scratch,zero plugins installed
disable all your wow addons and clear your wow cache



let us know
 
I tried all that, same error still. But it seems like it only crashes when I am AFK or simply not moving my mouse, I experimented about 3 hours, when I'm not moving my mouse at all it crashes in ~20-30 Minutes. If I move my mouse every 10 minutes it works fine. I could walk around that with some kind of macro tool or mouse-mover, whatever, but that's not what I'm expecting. The bot ran fine until last week when it started to crash.

And again, it happens right after an unstuck attempt:
Code:
[23:34:51:771] Activity: Unterwegs zum n?chsten Hotspot
[23:34:51:974] Spell_C::CastSpell(75207, 0, 0x0, 0) [595]
[23:34:56:517] [Flightor]: Unstuck attempt 23
[23:35:01:771] WoW wurde geschlossen, Honorbuddy wurde gestoppt!
[23:35:01:771] Stop called!

About 20 minutes after I stopped moving my mouse. Ran fine for about an hour while I was browsing around in the web.
 
Last edited:
I just recieved a PM from a user with the exact same problem, I'm not the only one it seems...

I'll try experimenting more this night.
 
all problems should go public tho,so we can catch bugs
 
He's got the same as mine, 20 mins AFK with bot --> Crash with wow error #132.
 
Sorry for the doublepost, but I want everybody to read it :)

This error can get fixed by downloading a tool that just moves your mouse every few seconds:
Mouse Mover, Download bei heise

It's german and all it sais is that it moves your mouse every few seconds by pressing start.

Anyways, by having my mouse moved WoW didn't crash for 4 hours.
 
Sorry for the doublepost, but I want everybody to read it :)

This error can get fixed by downloading a tool that just moves your mouse every few seconds:
Mouse Mover, Download bei heise

It's german and all it sais is that it moves your mouse every few seconds by pressing start.

Anyways, by having my mouse moved WoW didn't crash for 4 hours.

thx for sharing,idk if this issue has something to do with specific software or hardware setup...
 
Just to help out the situation a bit, I reformatted my PC a few weeks ago, it's Win7 64bit now, it was Vista 64bit before. Maybe it has something to do with it. Who knows, we have to wait for others with this problem.
 
Back
Top