66411fdd38
esp_ping_new_session can fail, particularly if ping is called quickly many times in succession. This is because `esp_ping_new_session` has to do a bunch of stuff including creating a task and a socket. Calling `esp_ping_delete_session` doesn't clean up these resources immediately. Instead, it signals the task to clean up resources and exit 'soon', but 'soon' is defined as 1 second. When the calls are frequent, the in-use sockets and tasks fill up available slots—I didn't actually check which resource gets used up first. With this change, the ping call will raise an exception instead of continuing with a call to esp_ping_start that crashes. Closes #5980 based on my testing on an ESP32S3-N8R2. |
||
|---|---|---|
| .. | ||
| Monitor.c | ||
| Monitor.h | ||
| Network.c | ||
| Network.h | ||
| Radio.c | ||
| Radio.h | ||
| ScannedNetworks.c | ||
| ScannedNetworks.h | ||
| __init__.c | ||
| __init__.h | ||