problem with bot 16 logout for inactivity

[alexio86]

hi,

after update bw i have this problem

16 bot stopped and logout for inactivity

what is problem?

log says so:

[19.18.34.172 D] Generating path to Loot Target <-332.8434, -25.46649, -0.519348>
[19.18.34.192 E] Contacting nav server for path.
[19.18.34.303 D] Waiting for path request to finish...
[19.18.34.372 D] Generating path to Loot Target <-332.8434, -25.46649, -0.519348>
[19.18.34.392 D] Waiting for path request to finish...
[19.18.34.416 D] Nav callback called.
[19.18.34.455 D] Generating path to Loot Target <-332.8434, -25.46649, -0.519348>
[19.18.34.476 E] Got response from server, validating.
[19.18.34.476 E] Response has 3 hops. Converting to vectors and path queue.
[19.18.34.476 D] Nav Service path generated.
[19.18.34.476 D] Generated path to <-332.8434, -25.46649, -0.519348> (Loot Target) with 3 hops.
[19.18.34.539 D] Moving to next hop: <-333.025, -25.4078, -0.975>, T: None (Loot Target) D: 2,765986
[19.18.37.874 D] Moving to next hop: <-332.8434, -25.46649, -0.519348>, T: None (Loot Target) D: 0,5599698
[19.18.40.025 V] Blacklisting 2331F948AC for 00:01:00
[19.18.40.025 V] [Poi.Clear] Reason: Done Looting.
[19.18.40.060 D] [POI Set] Type: Hotspot
[19.18.40.154 D] Generating path to Hotspot <-349.9767, -23.97681, 9.871473>
[19.18.40.154 E] Contacting nav server for path.
[19.18.40.267 D] Waiting for path request to finish...
[19.18.40.305 D] Generating path to Hotspot <-349.9767, -23.97681, 9.871473>
[19.18.40.305 D] Waiting for path request to finish...
[19.18.40.382 D] Nav callback called.
[19.18.40.405 D] Generating path to Hotspot <-349.9767, -23.97681, 9.871473>
[19.18.40.405 E] Got response from server, validating.
[19.18.40.405 E] Response has 16 hops. Converting to vectors and path queue.
[19.18.40.405 D] Nav Service path generated.


after this char go afk and logout for inactivity. problem nav server?

same other 16 bots

please can help me for fix this problem or not there solution?


thanks

 

[Cryogenesis]

post full log

 

[stoiansl]

i have this problem last 2 days alot too more from other days normaly

 

[alexio86]

try this link for one of 16 bots log. i can post too other log

2015-01-07 16.32

thanks

 

[alexio86]

other log 2015-01-07 22.31(2)

 

[Cryogenesis]

Your bot craps out on Failed to ReadProcessMemory.
I had this too yesterday. will try to contact aevitas about this.

 

[alexio86]

thanks. still today seems to go better.
only sometimes had this problem.

 

[silentfu72]

thanks. still today seems to go better.
only sometimes had this problem.

I have also had issues with crashes this week. It will run for about 30 mins to an hour at most then seems to just crap out much like Alexio is describing. Haven't seen issues like this in a long time before this week. Usually can run for hours at a time.

 

[Cryogenesis]

I think most of us where running joes.
Joes had a shitload of handlers to improve stability and rehooking and what not.
this isnt in use anymore, unless you use joes routine...

(all theory in my head and untested)

 

[silentfu72]

I think most of us where running joes.
Joes had a shitload of handlers to improve stability and rehooking and what not.
this isnt in use anymore, unless you use joes routine...

(all theory in my head and untested)

I use Joes. Just started it and it ran for about 3 mins then "failed to load process memory." clicking stop then start gets the bot moving again. Very unusual.


View attachment 2015-01-09 13.50.txt

 

[stoiansl]

12:34:48.782 D] Failed to ReadProcessMemory

all my bots went offline for inactivity again no need to post log its same errors like Alexio

 

[silentfu72]

Is this being looked into??? Can't run the bot for more than 30 mins to an hour without it crapping out. This just started being an issue with recent releases of buddywing.