Figured out the issue. The problem was that because all task's entire stack space and "personal information" were layed out sequentially in memory, in a big 45KB block of statically-allocated ram, an out-of-bounds array access on another task (which sat in memory right before the task that panicked)...

I am facing an eerily similar issue, where a task that looks something like this (pseudocode): while (true) { log_stack(); // this gathers the task name and stack watermark, which eventually calls into `prvTaskCheckFreeStackSpace`, causing the same exact panic auto event = receive_event_from_freerto...

github issue : https://github.com/espressif/esp-idf/issues/12970 IDF version: release/v5.2 Board: ESP-WROOM-32D I am trying to connect my board to a DiFluid Microbalance scale that uses BLE. I used the bluedroid BLE gatt_client example as the base for my code with minor adaptations (I have ensured ...