Before you asking
Describe the bug
Environment
- OS: Arch Linux
- Container runtime: Docker
- Deployment: Dokploy (Dockerfile)
- Repository: AzurLaneAutoScript (master)
- Device: Waydroid (ADB over TCP)
- Resolution: 1280x720
Description
ALAS starts normally and successfully connects to the Android device via ADB.
However, after starting the first scheduled task, the process always stops at:
No exception is printed and no further logs are generated.
The last message is:
End of log queue handler loop
Logs
Scheduler: Start task `Commission`
[Screen_size] 1280x720
early_ocr_import start
Loading OCR dependencies
End of log queue handler loop
ADB connection is successful:
already connected to 192.168.240.112:5555
PackageName com.YoStarEN.AzurLane
UI get current page
Screen_size 1280x720
Expected behavior
ALAS should continue loading OCR and execute the scheduled task.
Actual behavior
The process stops after Loading OCR dependencies without any traceback or error message.
Additional information
- ADB works correctly.
- The game is detected.
- Screen capture works.
- Scheduler starts the task successfully.
- The problem appears only when OCR initialization begins.
Could this be caused by a missing dependency or an exception being swallowed during OCR initialization?
If there is a way to enable verbose logging for the OCR initialization stage, I'd be happy to test it.
To Reproduce
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Expected behavior
No response
Relevant log output
Screenshots
Anything else?
No response
Before you asking
Describe the bug
Environment
Description
ALAS starts normally and successfully connects to the Android device via ADB.
However, after starting the first scheduled task, the process always stops at:
No exception is printed and no further logs are generated.
The last message is:
Logs
ADB connection is successful:
Expected behavior
ALAS should continue loading OCR and execute the scheduled task.
Actual behavior
The process stops after
Loading OCR dependencieswithout any traceback or error message.Additional information
Could this be caused by a missing dependency or an exception being swallowed during OCR initialization?
If there is a way to enable verbose logging for the OCR initialization stage, I'd be happy to test it.
To Reproduce
Expected behavior
No response
Relevant log output
Screenshots
Anything else?
No response