What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

why there are so many Execution of the block??

henryhut

New Member
Joined
Sep 26, 2012
Messages
7
Reaction score
0
Hi Dears,
My bot always say " Execution of the block..." and that makes game running lag..
Is there anything I can do to improve it?

[Trinity][Performance] Execution of the block NavigateTo took 1511.14ms.
[Trinity][Performance] Execution of the block NavigateTo took 290.60ms.
[Trinity] Your bot got stuck! Trying to unstuck (attempt #2 of 10 attempts) Act="OpenWorld" questId="312429" stepId="2" worldId="219659"
[Trinity][Performance] Execution of the block NavigateTo took 1505.72ms.
[Trinity][Performance] Execution of the block NavigateTo took 1271.50ms.
[Trinity] Your bot got stuck! Trying to unstuck (attempt #3 of 10 attempts) Act="OpenWorld" questId="312429" stepId="2" worldId="219659"
[Trinity][Performance] Execution of the block NavigateTo took 1504.50ms.
[Trinity][Performance] Execution of the block NavigateTo took 290.41ms.
[Trinity][Performance] Execution of the block NavigateTo took 1220.74ms.
[Trinity][Performance] Execution of the block NavigateTo took 263.02ms.
[Trinity][Performance] Execution of the block NavigateTo took 1150.37ms.
[Trinity][Performance] Execution of the block NavigateTo took 379.81ms.
[Trinity][Performance] Execution of the block NavigateTo took 1100.56ms.
[Trinity][Performance] Execution of the block NavigateTo took 1032.96ms.
[Trinity][Performance] Execution of the block NavigateTo took 262.28ms.
[Trinity][Performance] Execution of the block HandleTarget.HandleBasicMovement took 263.08ms.
[Trinity][Performance] Execution of the block HandleTarget took 264.63ms.
[Trinity][Performance] Execution of the block NavigateTo took 1242.76ms.
[Trinity][Performance] Execution of the block HandleTarget.HandleBasicMovement took 1243.51ms.
[Trinity][Performance] Execution of the block HandleTarget took 1251.29ms.
[Trinity][Performance] Execution of the block NavigateTo took 329.37ms.
[Trinity][Performance] Execution of the block NavigateTo took 1229.09ms.
[Trinity][Performance] Execution of the block NavigateTo took 284.77ms.
[Trinity][Performance] Execution of the block NavigateTo took 262.93ms.
[Trinity][Performance] Execution of the block NavigateTo took 273.01ms.
[Trinity][Performance] Execution of the block NavigateTo took 288.42ms.
[Trinity][Performance] Execution of the block NavigateTo took 277.11ms.
[Trinity][Performance] Execution of the block NavigateTo took 261.48ms.
[Trinity][Performance] Execution of the block NavigateTo took 278.14ms.
[Trinity][Performance] Execution of the block NavigateTo took 305.82ms.
[Trinity][Performance] Execution of the block NavigateTo took 322.33ms.
[Trinity][Performance] Execution of the block NavigateTo took 271.19ms.
[Trinity][Performance] Execution of the block HandleTarget.HandleBasicMovement took 272.01ms.
[Trinity][Performance] Execution of the block HandleTarget took 275.93ms.
[Trinity][Performance] Execution of the block NavigateTo took 495.30ms.
[Trinity][Performance] Execution of the block NavigateTo took 315.52ms.
[Trinity][Performance] Execution of the block NavigateTo took 328.90ms.
[Trinity][Performance] Execution of the block HandleTarget.HandleBasicMovement took 329.79ms.
[Trinity][Performance] Execution of the block HandleTarget took 333.95ms.
[Trinity][Performance] Execution of the block NavigateTo took 555.27ms.
[Trinity][Performance] Execution of the block HandleTarget.HandleBasicMovement took 555.97ms.
[Trinity][Performance] Execution of the block HandleTarget took 570.88ms.
[Trinity][Performance] Execution of the block NavigateTo took 395.94ms.
[Trinity][Performance] Execution of the block HandleTarget.HandleBasicMovement took 396.95ms.
[Trinity][Performance] Execution of the block HandleTarget took 408.98ms.
[Trinity][Performance] Execution of the block NavigateTo took 336.25ms.
[Trinity][Performance] Execution of the block HandleTarget.HandleBasicMovement took 337.03ms.
[Trinity][Performance] Execution of the block HandleTarget took 341.97ms.
[Trinity][Performance] Execution of the block NavigateTo took 285.64ms.
[Trinity][Performance] Execution of the block NavigateTo took 365.36ms.
[Trinity][Performance] Execution of the block NavigateTo took 333.93ms.
[Trinity][Performance] Execution of the block NavigateTo took 707.28ms.
[Trinity][Performance] Execution of the block HandleTarget.HandleBasicMovement took 708.24ms.
[Trinity][Performance] Execution of the block HandleTarget took 712.49ms.
[Trinity][Performance] Execution of the block NavigateTo took 318.56ms.
[Trinity][Performance] Execution of the block HandleTarget.HandleBasicMovement took 319.29ms.
[Trinity][Performance] Execution of the block HandleTarget took 336.62ms.
[Trinity][Performance] Execution of the block NavigateTo took 354.14ms.
[Trinity][Performance] Execution of the block HandleTarget.HandleBasicMovement took 354.91ms.
[Trinity][Performance] Execution of the block HandleTarget took 372.63ms.
[Trinity][Performance] Execution of the block NavigateTo took 302.59ms.
[Trinity][Performance] Execution of the block NavigateTo took 323.46ms.
[Trinity][Performance] Execution of the block HandleTarget.HandleBasicMovement took 324.28ms.
[Trinity][Performance] Execution of the block HandleTarget took 325.68ms.
[Trinity][Performance] Execution of the block NavigateTo took 378.71ms.
[Trinity][Performance] Execution of the block HandleTarget.HandleBasicMovement took 379.50ms.
[Trinity][Performance] Execution of the block HandleTarget took 381.09ms.
[Trinity][Performance] Execution of the block NavigateTo took 346.28ms.
[Trinity][Performance] Execution of the block NavigateTo took 354.11ms.
[Trinity][Performance] Execution of the block NavigateTo took 451.58ms.
[Trinity][Performance] Execution of the block HandleTarget.HandleBasicMovement took 452.39ms.
[Trinity][Performance] Execution of the block HandleTarget took 454.06ms.
[Trinity][Performance] Execution of the block NavigateTo took 408.73ms.
[Trinity][Performance] Execution of the block HandleTarget.HandleBasicMovement took 409.42ms.
[Trinity][Performance] Execution of the block HandleTarget took 425.46ms.
[Trinity][Performance] Execution of the block NavigateTo took 261.98ms.
[Trinity][Performance] Execution of the block NavigateTo took 343.48ms.
[Trinity][Performance] Execution of the block NavigateTo took 357.87ms.
[Trinity][Performance] Execution of the block HandleTarget.HandleBasicMovement took 358.62ms.
 
I have the same issue.. slow as hell. If you use Trinity .17 you won't have it as often (at least I don't..)
 
I have the same issue.. slow as hell. If you use Trinity .17 you won't have it as often (at least I don't..)

I have the same issue too... ever since the update to DB, I will downgrade to Trinity .17 and try see if I get less issues.
 
same problem for me.


[Trinity][Performance] Execution of the block NavigateTo took 417.36ms.
[Trinity][Performance] Execution of the block NavigateTo took 427.79ms.
[Trinity][Performance] Execution of the block NavigateTo took 457.00ms.
[Trinity][Performance] Execution of the block HandleTarget.HandleBasicMovement took 457.67ms.
[Trinity][Performance] Execution of the block HandleTarget took 458.89ms.
[Trinity][Performance] Execution of the block NavigateTo took 691.44ms.
 
same here:

[Trinity][Performance] Execution of the block NavigateTo took 316.01ms.
[Trinity][Performance] Execution of the block HandleTarget.HandleBasicMovement took 316.51ms.
[Trinity][Performance] Execution of the block HandleTarget took 317.78ms.
[Trinity][Performance] Execution of the block NavigateTo took 515.76ms.
[Trinity][Performance] Execution of the block HandleTarget.HandleBasicMovement took 516.26ms.
[Trinity][Performance] Execution of the block HandleTarget took 518.08ms.
[Trinity][Performance] Execution of the block NavigateTo took 350.14ms.
[Trinity][Performance] Execution of the block HandleTarget.HandleBasicMovement took 350.64ms.
[Trinity][Performance] Execution of the block HandleTarget took 352.19ms.
[Trinity][Performance] Execution of the block NavigateTo took 349.02ms.
[Trinity][Performance] Execution of the block HandleTarget.HandleBasicMovement took 349.52ms.
[Trinity][Performance] Execution of the block HandleTarget took 350.80ms.
 
Getting this too and DB crashes after enough of this spam

2014-04-10 20:10:41,065 [1] INFO BotMain (null) - Stopping the bot.
2014-04-10 20:10:41,066 [1] DEBUG BotMain (null) - CurrentBot.Stop()
2014-04-10 20:10:41,066 [1] DEBUG BotMain (null) - Navigator.Clear()
2014-04-10 20:10:41,066 [1] DEBUG BotMain (null) - TreeHooks.Instance.ClearAll()
2014-04-10 20:10:41,067 [1] INFO RoutineManager (null) - Chose Trinity as your combat routine
2014-04-10 20:10:41,067 [1] DEBUG TreeHooks (null) - Replaced hook [RoutineCombat] c03dc3ec-c940-4546-962c-653e8dda58c6
2014-04-10 20:10:41,067 [1] DEBUG BotMain (null) - OnStop event
2014-04-10 20:10:41,068 [1] DEBUG BotMain (null) - OnStop Event Invoking
2014-04-10 20:10:41,068 [1] DEBUG ProfileOrderManager (null) - ProfileOrderManager.OnBotStop. Resetting caches.
2014-04-10 20:10:41,069 [1] DEBUG ProfileOrderManager (null) - Resetting current behavior.
2014-04-10 20:10:41,069 [Main Bot Thread] ERROR PerformanceLogger (null) - [Trinity][Performance] Execution of the block RefreshLoS.2 took 3159799.77ms.
2014-04-10 20:10:41,073 [Main Bot Thread] ERROR PerformanceLogger (null) - [Trinity][Performance] Execution of the block RefreshDiaObject.LoS took 3159803.26ms.
2014-04-10 20:10:41,075 [Main Bot Thread] ERROR Logger (null) - [Trinity] Error while refreshing DiaObject ActorSNO: 4747 Name: #"'&5476767654'2#"'&'&5427632#"'"#&'#&+""##"'&5432233;'&'&547;; Type: Monster Distance: 0
2014-04-10 20:10:41,077 [Main Bot Thread] ERROR Logger (null) - [Trinity] System.Threading.ThreadAbortException: Thread was being aborted.
at Trinity.Trinity.RefreshStepIgnoreLoS(Boolean AddToCache) in c:\Users\srthsrth\Documents\DB\Plugins\Trinity\Cache\RefreshObject.cs:line 941
at Trinity.Trinity.CacheDiaObject(DiaObject freshObject) in c:\Users\thsrhrs\Documents\DB\Plugins\Trinity\Cache\RefreshObject.cs:line 226
at Trinity.Trinity.RefreshCacheMainLoop() in c:\Users\rthshrsthsrtrhts\Documents\DB\Plugins\Trinity\Cache\RefreshObjects.cs:line 349
2014-04-10 20:10:41,081 [1] DEBUG MainWindow (null) - Forcing all open windows to close.
2014-04-10 20:10:41,080 [Main Bot Thread] ERROR PerformanceLogger (null) - [Trinity][Performance] Execution of the block CacheManagement.RefreshCacheMainLoop took 3159812.94ms.
2014-04-10 20:10:41,082 [Main Bot Thread] ERROR PerformanceLogger (null) - [Trinity][Performance] Execution of the block RefreshDiaObjectCache.UpdateBlock took 3159816.81ms.
2014-04-10 20:10:41,085 [Main Bot Thread] ERROR PerformanceLogger (null) - [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 3159819.00ms.
2014-04-10 20:10:41,087 [Main Bot Thread] ERROR PerformanceLogger (null) - [Trinity][Perfo
 
My diablo window becomes super laggy on .18 too so I switched to .17, seems better.
 
I have the same issue too... ever since the update to DB, I will downgrade to Trinity .17 and try see if I get less issues.

Although I did get lower lag times, it didn't fix the problem in the end.. Seems like it's a DB problem. Hope they fix it soon :-) (currently using the BETA build)
 
Same problem here .... bot running circle and fulling my log with [Trinity][Performance] Execution of the block .. i just dont get it, why it goes same routes over and over and over again.... why it cant go further ? why stop in exact same spot every time and turn around and repeating... like a bad hobbit,, there and back again (and again and again)
 
I had the same problem yesterday. Updated DemonBuddy to B355 using Trinity .18 and the issue was resolved. I believe it had to do with something the DB code.
 
I am also getting these errors to the point where the bot wont even move. Fresh install of DB .384 and EZupdate trinity to .20.
 
This is a Demonbuddy problem.

I downgraded from beta to release and those messages are very rare now.
 
Same here its there sinds the first release of db for 2.0
 
If no one noticed you also get more of these errors when the diablo servers are lagging, These errors are trinity lag errors.
 
Back
Top