Open filzek opened 4 days ago
@filzek Could you share more detail to reproduce this issue?
We have not yet found a straightforward way to replicate this process. However, our analysis so far indicates that btm_rrm_t is not being properly destroyed when the Wi-Fi/LWIP stack is reinitialized. This oversight results in the continuous creation of new tasks, leading to task duplication and potential resource exhaustion.
Wifi layer still being corrupted and will stop work in multitasking complex tasks. We have this problems for so many versions, we would like to know any true robust system running right now with esp32 without network issues. Seems that for the last 4 years the problem still the same Wifi stocks halts loose connection and never came back. Now tcp/ip layer with same proglems. SDK 5.3.1 not okay.
We really want to understand why things are this deeply bad in keep the connection working???? Why we need to create a lot of patches to try to make the wifi and ip stack barnacle workable in a production environment.
I am about to open to offer for thousands of USD to show that solution aren't working at all in the development level inside espressif and CPUs sold could be extremely effective and can't stand working in production environment.
Things already went too far and now true answer come to the table to solve it. Everyone in espressif push to one to another and no one there really calls it on!
It's time to someone come abroad and solve the problem with the wifi and ip layer, thousands of offline devices that need to be power off and power on again isn't a true solution for this kind of service.
@euripedesrocha can someone come abroad to solve the problem for real????
Wifi layer still being corrupted and will stop work in multitasking complex tasks. We have this problems for so many versions, we would like to know any true robust system running right now with esp32 without network issues. Seems that for the last 4 years the problem still the same Wifi stocks halts loose connection and never came back. Now tcp/ip layer with same proglems. SDK 5.3.1 not okay.
Do you mean the older sdk versions (e.g. 5.2.x, 5.1.x) also have the same issue?
Answers checklist.
General issue report
The SDK 5.3.1 has a very deep bug in the IP/WiFi stack where it get stucked in TCP mode, the UDP mode keep working.
Also the wifi act weird in de-handshake sometimes.
Using WebSocket make the problem to get worst.
Unique way to solve it to deinitialize the lwip and wifi, and recreat it all again.:
Merge branch 'bugfix/fix_some_wifi_bugs_241024_v5.3' into 'release/v5.3' fix(wifi): fix some wifi bugs 241024 v5.3 See merge request espressif/esp-idf!34420