Bot frozen after going into portal

[Mr T]

Appears the bot froze while going into the stairs/portal or at the end .. not sure;

Had to close and re-open d3 as the process was frozen.

 

[Tony]

Game client crashing as well?

 

[Pantop]

Same here, yeah game client doesn't respond, you have to shut it down and re open both game and the bot. To be honest it was happening all the time before the last update, it just happened again 2 times after the update.

 

[spectrusv]

Same here, I just purchased the license, got excited to use your service but it's really annoying to have it crash after around 1 hour. Pretty dissapointed to see the frozen game when I came back from work today.

 

[Mr T]

Game client crashing as well?

D3 freezes, demonbuddy log window freezes @ ‘oh look a portal to enter’ but is still responsive. (Ie: I was able to stop the bot)

ultimately had to close both and re-open

 

[ownoob]

I have the same issue too

 

[monakian]

Same.

 

[Gymtansmush]

Mine seems to freeze after 1-2 rifts. seems to be getting worse worse now. I just gave up trying to use it until a patch is made, hopefully soon. using windows 10.

 

[rngsus]

Same.. but my DB is still responsive.. after stopping and closing DB, D3 freeze ended and show error code 1016

 

[gkpknowing]

Hello folks,
what classes are you using ? Or do you recognise some specific crash pattern, something that always happens ?

 

[rngsus]

I can't confirm for sure but act 3 that round map going to cydaea.

 

[spectrusv]

Hello folks,
what classes are you using ? Or do you recognise some specific crash pattern, something that always happens ?

yellow portals to act IV i think, it's always when changing zone through portal that the freeze happens

 

[Mr T]

Frozen again - update logs attached. Demonbuddy client was responsive and closed after I terminating d3

 

[dj1125]

Same, d3 client crashing at the portal.
Demonhunter class.

 

[Eyvin]

So, the solution to this, if you're paying attention to your bot, and you notice it get stuck on a portal...you can stop the bot, and close DB...and Diablo should start responding...at least this way, you wont lose a rift if you're paying attention. Dunno if this helps your trouble shooting @Tony

 

[rngsus]

Jailer map .. 2nd time today

 

[Schumacher]

Try deleting the settings folder... it helps for a while, atleast for me

 

[Tony]

its under investigation

 

[rngsus]

Babysitting my bot and arrived at the jailer map.. if I don't do anything it freezes, if I force left click it, it shows :-

[Trinity 2.6.448] [Rift] Oh look! There is a portal over there, let's see what's on the other side.
[Trinity 2.6.448] Exception in NephalemRiftTag: System.NullReferenceException: Object reference not set to an instance of an object.
at Trinity.DbProvider.PlayerMover.NavigateTo(Vector3 destination, String destinationName) in C:\Users\user\Desktop\Demonbuddy 1.1.550\Plugins\Trinity\DbProvider\PlayerMover.cs:line 121
at Trinity.DbProvider.PlayerMover.MoveTo(Vector3 destination) in C:\Users\user\Desktop\Demonbuddy 1.1.550\Plugins\Trinity\DbProvider\PlayerMover.cs:line 59
at Trinity.Components.Coroutines.MoveTo.<>c__DisplayClass1_0.<Execute>b__1() in C:\Users\user\Desktop\Demonbuddy 1.1.550\Plugins\Trinity\Components\Coroutines\MoveTo.cs:line 63
at Buddy.Coroutines.Coroutine.2M`T<oX6%\[EWy:`K) \.Yzr\*?%.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at Trinity.Components.Coroutines.MoveTo.<Execute>d__1.MoveNext() in C:\Users\user\Desktop\Demonbuddy 1.1.550\Plugins\Trinity\Components\Coroutines\MoveTo.cs:line 63
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at Trinity.Components.Adventurer.Coroutines.UsePortalCoroutine.<Interact>d__27.MoveNext() in C:\Users\user\Desktop\Demonbuddy 1.1.550\Plugins\Trinity\Components\Adventurer\Coroutines\UsePortalCoroutine.cs:line 185
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at Trinity.Components.Adventurer.Coroutines.UsePortalCoroutine.<Interacting>d__24.MoveNext() in C:\Users\user\Desktop\Demonbuddy 1.1.550\Plugins\Trinity\Components\Adventurer\Coroutines\UsePortalCoroutine.cs:line 166
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at Trinity.Components.Adventurer.Coroutines.UsePortalCoroutine.<GetCoroutine>d__20.MoveNext() in C:\Users\user\Desktop\Demonbuddy 1.1.550\Plugins\Trinity\Components\Adventurer\Coroutines\UsePortalCoroutine.cs:line 97
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at Trinity.Components.Adventurer.Coroutines.UsePortalCoroutine.<UsePortal>d__3.MoveNext() in C:\Users\user\Desktop\Demonbuddy 1.1.550\Plugins\Trinity\Components\Adventurer\Coroutines\UsePortalCoroutine.cs:line 28
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at Trinity.Components.Adventurer.Coroutines.RiftCoroutines.RiftCoroutine.<EnteringExitPortal>d__66.MoveNext() in C:\Users\user\Desktop\Demonbuddy 1.1.550\Plugins\Trinity\Components\Adventurer\Coroutines\RiftCoroutines\RiftCoroutine.cs:line 963
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at Trinity.Components.Adventurer.Coroutines.RiftCoroutines.RiftCoroutine.<GetCoroutine>d__39.MoveNext() in C:\Users\user\Desktop\Demonbuddy 1.1.550\Plugins\Trinity\Components\Adventurer\Coroutines\RiftCoroutines\RiftCoroutine.cs:line 215
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at Trinity.ProfileTags.RiftProfileBehavior.<MainTask>d__22.MoveNext() in C:\Users\user\Desktop\Demonbuddy 1.1.550\Plugins\Trinity\ProfileTags\RiftTag.cs:line 74
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at Trinity.Components.QuestTools.BaseProfileBehavior.<Run>d__30.MoveNext() in C:\Users\user\Desktop\Demonbuddy 1.1.550\Plugins\Trinity\Components\QuestTools\BaseProfileBehavior.cs:line 102
[Trinity 2.6.448] Resetting ActorCache

 

[grindinghc]

Same issue. If I close DB, then D3 becomes responsive again.