Seite 1 von 1

[4.6.3.1] Bot Crash

Verfasst: Do 9. Feb 2017, 09:00
von giopappy
Hi All, since this new update my Bot randomly crashes. Windows error reporting window appears and in the windows events registry the error was logged. I've attached it. In Bot logs (debug level set) nothing appears.
My system is windows 7 64bit based
In previous version (4.6.3.2) that crashes rarely appear (~ 1 per week). Now 2 or 3 times a day.

Thank you

Re: [4.6.3.1] Bot Crash

Verfasst: Do 9. Feb 2017, 11:31
von Brummiheld82
It looks like he makes a crash when he tries to go to the pet dungeons.

Switch this function off and then you look how it behaves then.

Re: [4.6.3.1] Bot Crash

Verfasst: Do 9. Feb 2017, 11:59
von giopappy
Ok , I'll try it!

Re: [4.6.3.1] Bot Crash

Verfasst: Do 9. Feb 2017, 13:04
von giopappy
Crash again, even after I've disabled pet dungeons. Attached the error event . I've found also a file "Report.wer" linked to the error. I'm attaching that too

Re: [4.6.3.1] Bot Crash

Verfasst: Mi 15. Feb 2017, 08:55
von giopappy
Update: I've tried to disable: Arena, City Guard, all dungeons (except portals) but Bot crashes even 10 times a day. So I've tried to re-enable all these features and using the console instead of the bot. In the last 24h no crashes. I'll go on using console, looking forward from a fixing in the next bot release.

Re: [4.6.3.1] Bot Crash

Verfasst: Do 23. Feb 2017, 09:59
von giopappy
Update: Using console, bot crashes anyway. I noticed that, during the weekend, crashes are more frequent.
Cause to an hd failure, I've installed from scrach (using a new hd) the so (always windows 7 64bit), so it shouldn't be an enviroment problem

Re: [4.6.3.1] Bot Crash

Verfasst: So 5. Mär 2017, 19:25
von boeserwolf
This is not an error related to any feature - it is related to the login/logout. It seems it occurs when the bot has been logged out by a browser connect.
We are investigating it.

Best regards
boeserwolf

Re: [4.6.3.1] Bot Crash

Verfasst: Fr 17. Mär 2017, 10:09
von boeserwolf
Hello giopappy,

The error will be fixed with the next version.

Best regards
boeserwolf