AFK bot much? :S

Sure, I'm not a lifetimer or anything like that, but if one pays for a feature, one expects that feature to fully function.

Now, I've had nothing but issues with running HB while AFK. Do I really need to babysit this bot? I mean, it's high tech and whatnot, but I didn't even have to babysit Glider back in the days, surely this bot can function without that need.

I dunno what issues I've gotten other nights, but I'm attaching a link for tonights log.

http://hb.lagnevall.com/2011_01_23_02_03_180_log.rar

Once a programmer has downloaded it, please delete the link from this post. Or I will delete the link manually as soon as I return home.

 

On the upside though, I am glad you guys fixed the Authentication issues, that was really grinding my nerves.

 

Great a log, but wait.. maybe mention what the issues you are experiencing?
Kinda need to know what to look for. Are you getting stuck? did wow exit? what?

 

From what I can see. It looks to be working until around 09:22 where you get

Code:

System.NullReferenceException: Object reference not set to an instance of an object.
   at dtNodePool.getNode(dtNodePool* , UInt32 id)
   at dtNavMeshQuery.initSlicedFindPath(dtNavMeshQuery* , UInt32 startRef, UInt32 endRef, Single* startPos, Single* endPos, dtQueryFilter* filter)
   at Tripper.RecastManaged.Detour.NavMeshQuery.InitSlicedFindPath(PolygonReference startRef, PolygonReference endRef, Vector3 startPos, Vector3 endPos, QueryFilter filter)
   at Tripper.Navigation.WowNavigator.FindPath(Vector3 start, Vector3 end)
   at Styx.Logic.Pathing.MeshNavigator.GeneratePath(WoWPoint from, WoWPoint to)
   at Styx.Logic.Pathing.Navigator.GeneratePath(WoWPoint from, WoWPoint to)
   at Bots.Grind.LevelBot.a(WoWObject A_0)
   at Bots.Grind.LevelBot.cj(Object A_0)
   at TreeSharp.Decorator.CanRun(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.Decorator.a.a()
   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.Decorator.a.a()
   at TreeSharp.Composite.Tick(Object context)
   at TreeSharp.PrioritySelector.a.b()
   at TreeSharp.Composite.Tick(Object context)
   at Styx.Logic.BehaviorTree.TreeRoot.b()

Until 09:32 where you either stop it or it closes itself

Code:

System.OutOfMemoryException: Ett undantagsfel av typen System.OutOfMemoryException uppstod.
   vid System.IO.MemoryStream.set_Capacity(Int32 value)
   vid System.IO.MemoryStream.EnsureCapacity(Int32 value)
   vid System.IO.MemoryStream.Write(Byte[] buffer, Int32 offset, Int32 count)
   vid System.Windows.Forms.RichTextBox.EditStreamProc(IntPtr dwCookie, IntPtr buf, Int32 cb, Int32& transferred)
   vid System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   vid System.Windows.Forms.NativeWindow.DefWndProc(Message& m)
   vid System.Windows.Forms.Control.DefWndProc(Message& m)
   vid System.Windows.Forms.Control.WndProc(Message& m)
   vid System.Windows.Forms.TextBoxBase.WndProc(Message& m)
   vid System.Windows.Forms.RichTextBox.WndProc(Message& m)
   vid System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   vid System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   vid System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Might have just been a fluke. Do this happen often? first time?

 

It happens alot, and its always HB that's crashed. (By crash I mean the process is not responding.)
WoW is just sitting idle in account login with the text Disconnected from Server (which it does after so and so long time of AFK.)

I believe this is the 6th or 7th night in a row that I wake up to the same thing, HB not responding and WoW sitting in account login screen.

I read there System.OutOfMemoryException, that has got to be impossible, WoW.exe process is currently at 650 MB, and I'm on a 4 Gig system, could there perhaps be a memory leak in HB that ultimately makes the system run out of memory or am I grasping for thin air here?

I would've loved to see this program working for me. :S

 

Oh and I was sound asleep between 02:30 through 10-11 in the morning.

I believe those 10 minutes to be the bot sitting there doing nothing and then WoW logging my char out.

 

Hey, this looks familiar. Woke up to the same thing.

I have yet to set it at night and wake up with it properly running in the morning.

 

Here, have another one.

 

Mine does too at least 3 times a day. HB will just stop responding and take up 100% of one of my cores. Wow goes idle and I get logged out. At least look at the bright side if you aren't logged in 100% of the time you don't look as much like a botter.

 

That statement holds truth! But it was extra annoying for me as I was having a race with another HB user, well, suffice to say, I'm now forced to monitor my HB while he made it to lvl 85 yesterday. :S
Anyhow, any HB programmer here that could perhaps shed some light on this issue? It seems that I'm not alone in the dark after all.

 

Third time today.