Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bot Exiting Mid-search/Mid-game #95

Open
Kyrluckechuck opened this issue Dec 11, 2024 · 4 comments
Open

Bot Exiting Mid-search/Mid-game #95

Kyrluckechuck opened this issue Dec 11, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@Kyrluckechuck
Copy link
Contributor

Kyrluckechuck commented Dec 11, 2024

Description

Hola folks!

Not sure what's changed in recent updates here that is affecting this, but something about the game loop appears to be exiting early with my setup. Currently running from latest main, with the attached config & log (with DEBUG logging enabled).
It looks like with the screen_record enabled: true flag set, it's encountering some sort of error and just aborting/exiting without any log to indicate why?

Basically I can start up the bot and it will nearly always immediately quit either after starting the search and before hitting accept, or just mid-game at some point.

Extra / Additional Info

exit-early.zip

Running:

  • Windows 11
  • Python 3.12.8
  • LDPlayer 9.1.26.3(64)

I've just reverted enabled: false for the screen_record setting and currently running through, will comment on this issue if it "resolves" it.
When enabled: true, it was a consistent behaviour over the last couple days.

@Kyrluckechuck Kyrluckechuck added the bug Something isn't working label Dec 11, 2024
@akshualy
Copy link
Contributor

Hi, the attached logs seem to not be from a session where you had screen record enabled, as it being enabled is logged. Could you check your other log files?

@Kyrluckechuck
Copy link
Contributor Author

Odd, I thought it had been -- this one specifically mentions it!
2024-12-10_22-14-13_979225.log

Also just confirming that disabling it worked as intended and ran overnight, so looks to be something specific to the recording flow

@akshualy
Copy link
Contributor

akshualy commented Dec 11, 2024

Thanks for reporting this, it's a little curious how nothing is logged because we have a broad exception catch for this exact reason.
I'll look into the reasons, if the process just got killed it might also be a performance related thing since screen recording usually takes a larger toll on system resources.
It'll take a bit longer as I'm in the process of a larger refactor, but once that is merged I can focus on features and fixes again.

@Kyrluckechuck
Copy link
Contributor Author

No worries -- it looks to be consistent for what that's worth, and I don't think it's related to high system resources but could very well be possible

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants