Crash/Panic when opening Recognition during first image capture

[Commifreak]

The Problem

When I try to open "Recognition" page during first image capture (directly after bootup) I get a system crash.
Not a big deal but maybe it can be catched.

Version

15.7.0

Logfile

[...]
[0d00h00m04s] 2025-01-27T19:19:08 <INF> [SNTP] Time is already set: 2025-01-27 19:19:08
[0d00h00m04s] 2025-01-27T19:19:08 <INF> [MAIN] CPU frequency: 160 MHz
[0d00h00m04s] 2025-01-27T19:19:08 <INF> [SDCARD] Folder/file presence check started...
[0d00h00m04s] 2025-01-27T19:19:08 <INF> [SDCARD] Folder/file presence check successful
[0d00h00m04s] 2025-01-27T19:19:08 <INF> [MAIN] Tag: 'v15.7.0', Release: v15.7.0 (Commit: 0d0b018+), Date/Time: 2024-02-17 00:15, Web UI: Release: v15.7.0 (Commit: 0d0b018+)
[0d00h00m05s] 2025-01-27T19:19:08 <WRN> [MAIN] Reset reason: Exception/panic
[0d00h00m05s] 2025-01-27T19:19:08 <WRN> [MAIN] Device was rebooted due to a software exception! Log level is set to DEBUG until the next reboot. Flow init is delayed by 5 minutes to check the logs or do an OTA update
[0d00h00m05s] 2025-01-27T19:19:08 <WRN> [MAIN] Keep device running until crash occurs again and check logs after device is up again
[0d00h00m05s] 2025-01-27T19:19:08 <INF> [LOGFILE] Set log level to DEBUG
[0d00h00m05s] 2025-01-27T19:19:08 <INF> [WLANINI] SSID: WLAN L22
[0d00h00m05s] 2025-01-27T19:19:08 <INF> [WLANINI] Password: XXXXXXXX
[...]
*crash happens again in debug mode*
[...]
[0d00h05m07s] 2025-01-27T19:28:08 <DBG> [MAIN SERVER] info_get_handler
[0d00h05m08s] 2025-01-27T19:28:09 <DBG> [MAIN SERVER] info_get_handler
[0d00h05m08s] 2025-01-27T19:28:09 <DBG> [OTA FILE] download_get_handler
[0d00h05m08s] 2025-01-27T19:28:09 <DBG> [MAIN SERVER] info_get_handler
[0d00h05m08s] 2025-01-27T19:28:09 <DBG> [MAIN SERVER] info_get_handler
[0d00h05m09s] 2025-01-27T19:28:10 <DBG> [MAIN SERVER] info_get_handler
[0d00h05m09s] 2025-01-27T19:28:10 <DBG> [MAIN SERVER] info_get_handler
[0d00h05m09s] 2025-01-27T19:28:10 <DBG> [OTA FILE] download_get_handler
[0d00h05m09s] 2025-01-27T19:28:10 <DBG> [MAIN SERVER] info_get_handler
[0d00h05m10s] 2025-01-27T19:28:10 <DBG> [OTA FILE] download_get_handler
[0d00h05m10s] 2025-01-27T19:28:10 <DBG> [MAIN SERVER] info_get_handler
[0d00h05m11s] 2025-01-27T19:28:12 <DBG> [PSRAM] Allocated 230400 bytes in PSRAM for 'C IMG BASIS->CImageBasis (rawImage)'
[0d00h05m11s] 2025-01-27T19:28:12 <DBG> [PSRAM] Allocated 128004 bytes in PSRAM for 'ALIGN->AlgROI'
[0d00h05m11s] 2025-01-27T19:28:12 <INF> [LOGFILE] Set log level to WARNING
[0d00h05m11s] 2025-01-27T19:28:12 <DBG> [MQTT] Digitizer interval is 5.0 minutes => setting MQTT LWT timeout to 12.5 minutes.
[0d00h05m11s] 2025-01-27T19:28:12 <DBG> [MQTT IF] URI: mqtt://192.168.178.5:1883, clientname: watermeter, user: ai_wasser, password: XXXXXXXX, maintopic: watermeter, last-will-topic: watermeter/connection, keepAlive: 750, RetainFlag: 0
[0d00h05m11s] 2025-01-27T19:28:12 <INF> [MQTT IF] Init
[0d00h05m11s] 2025-01-27T19:28:12 <INF> [MQTT IF] Client started, waiting for established connection...
[0d00h05m11s] 2025-01-27T19:28:12 <DBG> [MQTT IF] topic watermeter/ctrl/set_prevalue subscribe successful, msg_id=2
[0d00h05m11s] 2025-01-27T19:28:12 <INF> [MAINCTRL] Autostart is not enabled -> Not starting Flow
[0d00h00m00s] 2025-01-27T18:28:16 <INF> [MAIN] =================================================
[0d00h00m00s] 2025-01-27T18:28:16 <INF> [MAIN] ==================== Start ======================
[0d00h00m00s] 2025-01-27T18:28:16 <INF> [MAIN] =================================================

Expected Behavior

No response

Screenshots

No response

Additional Context

No response

[Commifreak]

Maybe important: For reasons, I turned off the auto Flow start option. So the AIOTED keeps the state "initializing" after bootup.

[Commifreak]

Auto Flow back to on but I was playing with the image without adjusting ROI's. So, nothing to detect. Then it happens as well, even after taking picture & aligning. As said: not a big deal (because misconfigured) but maybe we can catch the sw panic?

[caco3]

Maybe important: For reasons, I turned off the auto Flow start option. So the AIOTED keeps the state "initializing" after bootup.

this is to be expected when you disable the auto start functionality. In fact there is no valid use case with it disabled, thus it will get removed in the next release.

Can you try with a different SD card and power supply?
Also try with the latest pre-release, there are some huge improvements.

[Commifreak]

Latest RC has same issue: If no Digit recognition is done, The Recognition page causes a crash. It doesnt feel like an power/sdcard issue, because the system is running for days now without reboot. But if you are curios, I can test it.

Is there a way to get the crash captured via USB?