![]() waiting for completion (pending request) - Settings: cycles: 999, breaks: 25 - 35, max dist: 50, web-browser-user-profile-id: default - Web browser framework status: Last script run result is: Error: Exception from volatile process: System.AggregateException: One or more errors occurred. Current activity: + Waiting because reloaded web page 9 seconds ago. Started the web browser 308 times, last time was 0 minutes ago. Checked 1471 unique coordinates and found 174 villages, 59 of which are barbarian villages. Status message from bot: Session performance: attacks sent: 59, coordinates read: 1641, completed farm cycles: 1 Completed first farm cycle 121 minutes ago with 2 villages (Attack limit: 1, Out of units: 1). There are 1 tasks in progress ( setup-11 ). Last bot event was 0 seconds ago at 22-02-56.559. Press SHIFT + CTRL + ALT keys to pause the bot. This is what it’s spitting out now.īot 2979167a62. It not giving the error message anymore but it still not able to properly re-launch the browser again. This screenshot shows how Task Manager displays information on memory usage: Independent of the information we get through the botlab client, we can use the Windows Task Manager app to check how much memory the browser uses. That might also help with these kinds of problems. ![]() I will look into updating the integrated web browser to a newer version. One thing you can do immediately is to change the in-game configuration to try to reduce memory usage. Since we now know which instance was affected, I can add functionality to monitor that instance to see how much it uses on your setup. The error message indicates a problem related to the amount of available memory. The session performance statistics we see in your texts help us understand how early in a session this problem occurred. The embedding, in turn, helps to see the relation to session duration and the duration since the last reopening of the web browser. One implication is that we will find the error message reflected in the session record. In that sample, I also see that the error came via the chrome instance controlled via the volatile process and not from the javascript engine that runs in the botlab client. Great, that gives a much more complete picture. # Fatal javascript OOM in Committing semi space failed. Settings: cycles: 999, breaks: 45 - 60, max dist: 50, web-browser-user-profile-id: default - Web browser framework status: Last script run result is: Success: Current activity: Operate bot. ![]() Current activity: + Next farm cycle starts in 16 minutes. Started the web browser 1 times, last time was 33 minutes ago. Checked 205 unique coordinates and found 12 villages, 6 of which are barbarian villages. Status message from bot: Session performance: attacks sent: 6, coordinates read: 211, completed farm cycles: 1 Completed first farm cycle 28 minutes ago with 1 villages (Attack limit: 1). Last bot event was 0 seconds ago at 06-22-35.919.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |