Open anszom opened 3 years ago
I forgot to mention - for the BT stress tests I'm using a Nexus 5 phone with the CrDroid ROM. The ROM has some bugs related to BT handling, and the BT controller on the phone occasionally crashes & restarts during the tests. It's possible that the BT crash on the phone triggers some unusual conditions which trigger the ESP32 bug - but I'm not sure if these are related. Anyway, it shouldn't be possible to crash the ESP32's bluetooth stack remotely.
Thanks for reporting, we will look into.
I have a similar issue reported in #6417. Occurs when operating as a BLE client, so not likely related to the phone.
Environment
git describe --tags
to find it): v4.2-beta1-202-g805a4d9b3, but see belowxtensa-esp32-elf-gcc --version
to find it): xtensa-esp32-elf-gcc (crosstool-NG esp-2020r1) 8.2.0Problem Description
I'm using ESP32 as a Bluetooth LE peripheral. I'm using nimble as the BT stack but it shouldn't matter. Under random circumstances, the BT controller library crashes. I've reduced my code to a minimal example which is available here. To stress-test the BT interface, I'm using a custom Android application (that I unfortunately can't share), that randomly connects, disconnects, sends and receives data from the ESP32 BLE peripheral. Reproducing the bug takes up to several hours with my setup.
The issue doesn't occur with IDF v4.1. Using git bisect, I've identified the commit which introduces the problem - df301b89ece5325b5a0125135e96540156c890cb.
Below is an example crash log produced with ESP-IDF version df301b89ece5325b5a0125135e96540156c890cb