Missing 11 bytes from TCP download when ESP_AUTO_RECV set
Posted: Sun Sep 18, 2022 8:52 pm
I know this is ancient history at this point, but we are narrowing down a bug in our OTAU which often* results in 11 bytes missing from a TCP stream. That is, we `read` from the socket, and the total number of bytes that we are able to read is 11 less than is seen in Wireshark. Somewhere in lwIP those 11 bytes are being dropped.
(*) This used to happen only seldom, or for users with high-latency internet connections. Then it has occurred more frequently to the point that units are nearly un-upgradable. Thankfully we can also update from the HTTP server embedded in our app.
I found that disabling ESP_AUTO_RECV makes the problem go away. I suspect some kind of thread safety issue.
The question: Can anyone shed more light on this "ESP_AUTO_RECV" function? Why was it added? Was this an optimization? What can be expected when we disable it?
We are on ESP-IDF v3.3.4.
Commit that introduced ESP_AUTO_RECV: https://github.com/espressif/esp-lwip/c ... 4ffd7dc2a8
(*) This used to happen only seldom, or for users with high-latency internet connections. Then it has occurred more frequently to the point that units are nearly un-upgradable. Thankfully we can also update from the HTTP server embedded in our app.
I found that disabling ESP_AUTO_RECV makes the problem go away. I suspect some kind of thread safety issue.
The question: Can anyone shed more light on this "ESP_AUTO_RECV" function? Why was it added? Was this an optimization? What can be expected when we disable it?
We are on ESP-IDF v3.3.4.
Commit that introduced ESP_AUTO_RECV: https://github.com/espressif/esp-lwip/c ... 4ffd7dc2a8