Application crash randomly after a while
Closed this issue · 12 comments
Describe the bug
The Application crashes randomly after running for a while
To Reproduce
Steps to reproduce the behavior:
Create a new smartdetection event with at least 2 event and image detection, add a button click event of 100ms and a delay 1second before and after the click.
run the task ensuring it find something to click and after a while it crashes.
Expected behavior
It should keep running.
Log attached:
SmartAutoclickerCrashLogcat.txt
Smartphone (please complete the following information):
- Device: xiaomi red mi note 7 (also reproduced in 3 different emulators with android 10 and 13)
- Android OS version: 10
- Smart AutoClicker version: current
exprenced the same any update ?
the issue has NOT been fixed even at commit: 07a8d39
Issue cannot be reproduced on 2.4.2 on my devices. Can you provide a scenario backup zip file containing only the steps to reproduce the issue ?
Please note: I only provide support for official versions downloaded on Fdroid or Google PlayStore
I cannot send it right now, but i can tell you that after 15 minutes max of the app running and looking for matches of images (at least 2 conditions) it crashes.
Yeah i know i hoped that your git was ahead and so i tried it still the same behavior.
Btw I paid for it before i knew it was broken because the ease of use was excelent, with this problem fixed it will become a great app 👍
Can you try with this test apk if you can reproduce the issue?
Do not use any of the new Trigger Event features as they are not tested and might interfere with the test.
Logs:
Header |
---|
2024-05-07 11:49:08.686 1901-4670 EGL_emulation com.buzbuz.smartautoclicker.debug D app_time_stats: avg=1499.77ms min=1499.77ms max=1499.77ms count=1 |
2024-05-07 11:49:17.419 1901-4670 EGL_emulation com.buzbuz.smartautoclicker.debug D app_time_stats: avg=8732.44ms min=8732.44ms max=8732.44ms count=1 |
2024-05-07 11:49:18.920 1901-4670 EGL_emulation com.buzbuz.smartautoclicker.debug D app_time_stats: avg=1500.88ms min=1500.88ms max=1500.88ms count=1 |
2024-05-07 11:49:29.896 1901-2423 Detector com.buzbuz.smartautoclicker.debug E ROI is invalid, 212/726 87/ 90 in 3025/ 3125 |
2024-05-07 11:49:29.905 1901-2423 Detector com.buzbuz.smartautoclicker.debug E ROI is invalid, 436/299 87/ 90 in 3025/ 3125 |
2024-05-07 11:49:42.738 1901-2423 Detector com.buzbuz.smartautoclicker.debug E ROI is invalid, 212/726 87/ 90 in 3025/ 3125 |
2024-05-07 11:49:42.761 1901-2423 Detector com.buzbuz.smartautoclicker.debug E ROI is invalid, 436/299 87/ 90 in 3025/ 3125 |
2024-05-07 11:50:02.366 1901-2423 Detector com.buzbuz.smartautoclicker.debug E ROI is invalid, 212/726 87/ 90 in 3025/ 3125 |
2024-05-07 11:50:02.393 1901-2423 Detector com.buzbuz.smartautoclicker.debug E ROI is invalid, 436/299 87/ 90 in 3025/ 3125 |
---------------------------- PROCESS ENDED (1901) for package com.buzbuz.smartautoclicker.debug ---------------------------- |
---------------------------- PROCESS STARTED (5413) for package com.buzbuz.smartautoclicker.debug ---------------------------- |
2024-05-07 11:50:57.870 5413-5525 QualityManager com.buzbuz.smartautoclicker.debug I Smart AutoClicker has crashed during it's last session ! |
Is this test made with the provided apk ?
This invalid ROI is related to the scenario configuration, once again i can't reproduce it as long as you don't provide me your scenario-backup zip file.
The latest log is printed by Smart autoclicker but is irrelevant when using it in a non production use case like you. In your first complete log, there is no trace of crash of the app, only an out of memory issue that can be explained by an invalid compilation setup.
SmartAutoClicker-Backup.zip
yes the test was made with the provided apk, but it doesn't matter the scenario or the images it works great then after 10 min it crashes for no reason on both emulators and xiaomi devices
Have the same Problem. And after the Crash the App doenst Accept that i gave it the permissions (its allowed) and have to Reboot my phone
Xiaomi
Please try using the latest 3.00v4 Beta version
Closed: old issue format. If this still happen on current versions, please open a new ticket.