"object reference not set to an instance of an object"

ive been having the same troubles. i also get the random dumps were it shows no reason for it in the logs

 

SAME PROBLEM!!!

Crashed all night .

I can't run it anymore. Happens on all chars, all profiles.

This only started happening on the new release from yesterday.

Any ideas devs?

TY!!!!!!!

 

same here

 

Same

 

same, i've tried to submit a few of the logs through the bug submitter

 

Thank goodness for logs, I recieved the same crash as above after 4 hours of running around questing and saving all the data to make a quest profile.. then BAM, it crashed with that fault {OBJECT REF.} The log file was nice enough to have stored all the data, learned something new today.

 

[6:30:32 PM:905] Activity: Combat
[6:30:33 PM:765] System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.WaitHandle.WaitOneNative(SafeWaitHandle waitHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
at System.Threading.WaitHandle.WaitOne(Int64 timeout, Boolean exitContext)
at System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout, Boolean exitContext)
at BlueMagic.ExecutorRand.Execute()
at Styx.WoWInternals.WoWMovement.a(ClickToMoveType A_0, UInt64 A_1, WoWPoint A_2, Single A_3)
at Styx.WoWInternals.WoWMovement.ClickToMove(UInt64 guid, ClickToMoveType type)
at Styx.WoWInternals.WoWMovement.a(UInt64 A_0, Boolean A_1)
at Styx.WoWInternals.WoWMovement.ConstantFace(UInt64 guid)
at Styx.WoWInternals.WoWMovement.Face()
at Convalesce.Paladin.Checks()
at Convalesce.Paladin.Combat()
at Bots.Grind.LevelBot.ck(Object A_0)
at TreeSharp.Action.RunAction(Object context)
at TreeSharp.Action.a.a()
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.Sequence.a.b()
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.PrioritySelector.a.b()
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.PrioritySelector.a.b()
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.Decorator.a.a()
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.PrioritySelector.a.b()
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.PrioritySelector.a.b()
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.PrioritySelector.a.b()
at TreeSharp.Composite.Tick(Object context)
at Styx.Logic.BehaviorTree.TreeRoot.b()
[6:30:33 PM:765] Cleared POI
[6:30:33 PM:766] Stop Button pressed. User has stopped the bot.


yep... but boss says the next release (tonight or tomorrow) is a lot more stable

 

Same. I've tried Mixed mode and Grinding. Happens on both of them at no specific time, event intervals. Just out of the blue it appears. My logs look the same as others, have posted to the BugTracker.

 

can't wait for the new release...the current is better then the test ones before but compared to 3.3.5 not stable at all

 

****EDIT: NEVERMIND!!!!! Just happened again with the latest vers. -_-'

 

I get this problem too, can only bot whilst keeping an eye on it as it it crashes ever hour or so. Please fix this soon

 

Ah! There's been an update. Thanks for letting me know, much appreciated

 

Tried new vers... same bug, but not it comes with this LONG string of junk included in the error popup.



any ideas

 

Here's my log:

Error starts "[8:08:12 AM:187]"

 

Okay, I left 2 bots on all night. They ran perfect like a dream, even into the whole day for a few hours so total run time was around 10 hours. I was stoked thinking it was fixed, but then I got the error again!

It seems like it'll just happen randomly... either right at first or later.

When the realms go back online I'll do another full day test and report back. I'll post up a log w/ the other char it happens on too.

Thanks for your help!!!!

P.S. I'm thinking it *is* an internet authentication issue. Like, maybe when my internet 'hiccups' and temporarily disconnects it screws up then? I noticed when the error happened earlier tonight (After the 10 hour long botting sesh) it was when my internet temporarily failed due to maintenance or some b.s.)

Again will test some more and report back.

Cheers!