Alright so I had well over 450 hours+ running this same DB beta, trinity, and questtools since 2.1 update. No issues, I had about 2 battle.net upgrades from the starter(no patches, not sure if this has anything to do with it) after that I began getting my games freezing at random periods, It could be 15 minutes into starting my bot it could be an hour or two hours later. I have since Upgraded to the latest DB beta + Trinity + QT as well as tried the recommended versions for yet another rifters compilation. No matter what changes it always freezes sooner or later. I AM running kadalaspree, But if kadala ever bugs(rarely ever does) it never crashed the game just sat there til timer expired that was all. I have numerous logs, So I will post the most recent updated version one that crashed something like 15 minutes in
In the log, you can skip forward to 17:17:06.975 timestamp, and thats when the issue shows up. Every time I see the frozen screen there is nothing special about it. sometimes RG is up, sometimes its 10% into a rift, sometimes halfway or 80%. I must add I am in fact running custom loot rules by Job(which for some reason the bot seems to now pickup the occasional rare weapon/armor despite it set not to pick these up. One more thing thats slightly lesser of a concern, it appears with the new update of either trinity or QT or maybe DB whatever did it. I can no longer pause my bot while it has items in his inventory, and either salvage or stash them unid/id on my own. Because Upon unpausing it spams bullshit about backpack and coroutine townrun junk and only way to fix it to stop start bot.
This is the error I receive, I noticed others getting this too and I tried all of the other fixes that were suggested(changing d3 to higher then normal process, upgrading DB/Trinity/QT etc)
17:16:50.685 DEBUG Logger [ExploreDungeonTag] Nodes [Unvisited: Route:35 Grid:35 | Grid-Visited: 18/53] Box:30/0.15 Step:MainBehavior PP:10 Dir: E Current: 261, 411, 0
17:16:51.945 DEBUG Logger [ExploreDungeonTag] Nodes [Unvisited: Route:35 Grid:35 | Grid-Visited: 18/53] Box:30/0.15 Step:MainBehavior PP:10 Dir: SE Current: 261, 411, 0
17:17:06.975 ERROR BotMain Exception during bot tick.
System.Exception: Process must have frozen or gotten out of sync: InjectionFinishedEvent_was_never_fired
at GreyMagic.Executor.WaitForInjection(Int32 timeout)
at GreyMagic.Executor.Execute(Int32 timeout)
at GreyMagic.Executor.GrabFrame()
at GreyMagic.ExternalProcessMemory.AcquireFrame(Boolean isHardLock)
at Zeta.Bot.BotMain.()
Currently running:
DemonbuddyBETA v1.1.2180.496
Trinity v2.2.0
QuestTools v3.0.6
Kadala 2.3.2(downgraded because latest does not work, Was previously using an older version pre 25shards per by using settings that would work around the price change that worked fine but upgraded anyway to see if kadalaspree was it)
Running t6 rifts over and over and over. Not a clue whats causing this, Sometimes I see botmemory exception spam too. and thats something I never saw unless I used boon of the hoarder gem. Anyway thats 3 issues, 2 minor at best. I really just want to figure out how to get my bot to stop freezing. I am not new to this, So like I said before I have done fresh reinstalls, I have tried it with and without kadalaspree. The one thing I did not try was switching back to trinity loot rules instead of jobs loot rules but I fail to see how that would crash the bot.
Starting my bot again to see how long it will last for, If I get a crash again I will try going back to trinity loot rules to test that theory out although auto salvaging junk items was alot nicer. Anymore info needed pls ask.
In the log, you can skip forward to 17:17:06.975 timestamp, and thats when the issue shows up. Every time I see the frozen screen there is nothing special about it. sometimes RG is up, sometimes its 10% into a rift, sometimes halfway or 80%. I must add I am in fact running custom loot rules by Job(which for some reason the bot seems to now pickup the occasional rare weapon/armor despite it set not to pick these up. One more thing thats slightly lesser of a concern, it appears with the new update of either trinity or QT or maybe DB whatever did it. I can no longer pause my bot while it has items in his inventory, and either salvage or stash them unid/id on my own. Because Upon unpausing it spams bullshit about backpack and coroutine townrun junk and only way to fix it to stop start bot.
This is the error I receive, I noticed others getting this too and I tried all of the other fixes that were suggested(changing d3 to higher then normal process, upgrading DB/Trinity/QT etc)
17:16:50.685 DEBUG Logger [ExploreDungeonTag] Nodes [Unvisited: Route:35 Grid:35 | Grid-Visited: 18/53] Box:30/0.15 Step:MainBehavior PP:10 Dir: E Current: 261, 411, 0
17:16:51.945 DEBUG Logger [ExploreDungeonTag] Nodes [Unvisited: Route:35 Grid:35 | Grid-Visited: 18/53] Box:30/0.15 Step:MainBehavior PP:10 Dir: SE Current: 261, 411, 0
17:17:06.975 ERROR BotMain Exception during bot tick.
System.Exception: Process must have frozen or gotten out of sync: InjectionFinishedEvent_was_never_fired
at GreyMagic.Executor.WaitForInjection(Int32 timeout)
at GreyMagic.Executor.Execute(Int32 timeout)
at GreyMagic.Executor.GrabFrame()
at GreyMagic.ExternalProcessMemory.AcquireFrame(Boolean isHardLock)
at Zeta.Bot.BotMain.()
Currently running:
DemonbuddyBETA v1.1.2180.496
Trinity v2.2.0
QuestTools v3.0.6
Kadala 2.3.2(downgraded because latest does not work, Was previously using an older version pre 25shards per by using settings that would work around the price change that worked fine but upgraded anyway to see if kadalaspree was it)
Running t6 rifts over and over and over. Not a clue whats causing this, Sometimes I see botmemory exception spam too. and thats something I never saw unless I used boon of the hoarder gem. Anyway thats 3 issues, 2 minor at best. I really just want to figure out how to get my bot to stop freezing. I am not new to this, So like I said before I have done fresh reinstalls, I have tried it with and without kadalaspree. The one thing I did not try was switching back to trinity loot rules instead of jobs loot rules but I fail to see how that would crash the bot.
Starting my bot again to see how long it will last for, If I get a crash again I will try going back to trinity loot rules to test that theory out although auto salvaging junk items was alot nicer. Anymore info needed pls ask.
