Character randomly doesn't engage in combat for a few seconds

[TC9869]

Sometimes, the bot seems to stop thinking for a few seconds.. it doesn't react to getting attacked, and it seems to basically try to run into a wall or something. I'm doing a zone I've been farming for weeks without issue until the past few days, so this is a pretty new issue (maybe 3-4 days). I just assumed this would have already been reported but browsing the forums I haven't seen a similar report, unless I missed it.

No new log messages appear during this time, but at the end I get an exception like this:

Error during bot tick: System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 5D4C0000, Size: 8
at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
at GreyMagic.MemoryBase.Read[T](IntPtr addr)
at Loki.Game.Std.Containers.StdVector[TValue](NativeVector nativeVector, ExternalProcessMemory m)
at Loki.Game.Objects.Components.ObjectMagicPropertiesComponent..
()
at System.Linq.Enumerable.<UnionIterator>d__88`1.MoveNext()
at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source, Func`2 predicate)
at Loki.Game.Objects.Actor.GetStat(StatType stat)
at Loki.Game.Objects.Monster.get_IsHidden()
at Loki.Game.Objects.Monster.get_IsActive()
at GrindBot7.GrindBot.
(Monster )
at System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext()
at System.Linq.Enumerable.<UnionIterator>d__88`1.MoveNext()
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at GrindBot7.GrindBot.
()
at GrindBot7.GrindBot.UpdateExploration()
at GrindBot7.GrindBot.Pulse()
at Loki.Bot.Pulsator.
(PulseFlags , PulseFlags , Action , String )
at Loki.Bot.Pulsator.Pulse(PulseFlags flags)
at Loki.Bot.BotMain.()

 

[pushedx]

This is something that can happen time to time as a result of being an out of process bot. Memory gets moved around or something changes faster than the bot can process, and as a result, bad memory is read. The bot takes a few ticks to recover, but should continue on. There's a few core changes going to be made soon that should address random performance spikes, but overall, there's nothing else we can do to avoid this issue.