conditions for closing the bot process

Question

conditions for closing the bot process

Levris opened this issue a year ago · comments

it 's very strange that the bot worked fine all night, but when I got up in the morning , I found the ship in the dock and the bot process is simply missing, it looks like a client crash or are there conditions that complete the bot process and it closes ?

Michael Rätzel · Answer 1 · Sat Apr 22 2023 20:59:47 GMT+0800 (China Standard Time)

That sounds strange. The BotLab client has no functionality to close automatically.
If there is an error, it usually displays a message in a popup window.
If the BotLab client window or process is gone, I see two places to look for more information about a crash:

The log file created by the BotLab client process on startup in %localappdata%/botlab/local-instance
The Windows Event Viewer

If a BotLab client process crashes, we will find an entry in the Windows Event Viewer representing that process crash. And that, in turn, contains a stack trace that will help us identify the cause.

Levris · Answer 2 · Sat Apr 22 2023 23:44:46 GMT+0800 (China Standard Time)

im find a problem [image: image.png] сб, 22 апр. 2023 г. в 15:59, Michael Rätzel ***@***.***>:

…

That sounds strange. The BotLab client has no functionality to close automatically. If there is an error, it usually displays a message in a popup window. If the BotLab client window or process is gone, I see two places to look for more information about a crash: 1. The log file created by the BotLab client process on startup in %localappdata%/botlab/local-instance [image: image] <https://user-images.githubusercontent.com/19209696/233786225-6a7fc39a-479f-427e-ba33-ca31d835dc71.png> 2. The Windows Event Viewer [image: image] <https://user-images.githubusercontent.com/19209696/233786245-f26e65a2-0fc2-4c6f-ba57-ee96905aa4b1.png> If a BotLab client process crashes, we will find an entry in the Windows Event Viewer representing that process crash. And that, in turn, contains a stack trace that will help us identify the cause. — Reply to this email directly, view it on GitHub <#80 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHE6FHCHKLKJI3YUTOKDJCDXCPI43ANCNFSM6AAAAAAXHYBZRA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

Michael Rätzel · Answer 3 · Mon Apr 24 2023 22:31:50 GMT+0800 (China Standard Time)

im find a problem

Did you find a problem?
If you have an image, you can attach it here in the GitHub issue thread.

Levris · Answer 4 · Tue Apr 25 2023 00:14:39 GMT+0800 (China Standard Time)

Here it is. the problem turned out to be the overcrowding of the folder on the c drive in which the bot's log is recorded пн, 24 апр. 2023 г. в 17:32, Michael Rätzel ***@***.***>:

…

im find a problem Did you find a problem? If you have an image, you can attach it here in the GitHub issue thread. — Reply to this email directly, view it on GitHub <#80 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHE6FHAYO7QV66US4Y43BFTXC2FGDANCNFSM6AAAAAAXHYBZRA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

Michael Rätzel · Answer 5 · Tue Apr 25 2023 01:55:20 GMT+0800 (China Standard Time)

Thank you for the update! Seeing this, it would be better if there was some warning signal in the UI to alert when there is not much space left.

To avoid this problem, you can configure it to store the play sessions on another drive.
You can use the 'Client Settings' dialog to choose any directory as target:

This feature is available in newer versions, including 2023-04-23.