You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi
I noticed something strange. If a client disconnects from the telnet server suddenly, the ESP goes into an endless loop. At the same time, I don’t see the watchdog triggering and ESP reboots.
ESP comes to life if:
forcibly disconnect the ESP client on the wifi router
reconnect to the telnet server
It feels like there is somewhere stuck in an infinite loop with a call to yield() because the watchdog timer is not firing.
This can be easily tested:
We use ESPTelnet and Pubsubclient
Every 5 seconds we write something in the mqtt topic and in telnet
Connect to the telnet server
Disable wifi on the telnet client without terminating the session in the telnet client
We see that mqtt client on ESP has stopped publishing messages
I tested this on ESP8266 and ESP32, the behavior is the same. If I end the session in the telnet client, this does not occur.
It looks like the TCP connection is stuck. It appears that the TCP connection is waiting for a response from the client. But I didn’t see any bugs in your code, performKeepAliveCheck should disconnect the client, but something prevents it from doing this.
Do you have any ideas?
The text was updated successfully, but these errors were encountered:
Hi
I noticed something strange. If a client disconnects from the telnet server suddenly, the ESP goes into an endless loop. At the same time, I don’t see the watchdog triggering and ESP reboots.
ESP comes to life if:
It feels like there is somewhere stuck in an infinite loop with a call to yield() because the watchdog timer is not firing.
This can be easily tested:
I tested this on ESP8266 and ESP32, the behavior is the same. If I end the session in the telnet client, this does not occur.
It looks like the TCP connection is stuck. It appears that the TCP connection is waiting for a response from the client. But I didn’t see any bugs in your code, performKeepAliveCheck should disconnect the client, but something prevents it from doing this.
Do you have any ideas?
The text was updated successfully, but these errors were encountered: