@Gordon Yes during the dump the clients failed to receive anything and wireshark showed only HTTP requests but not replies. I can reproduce the situation by first adding clients and in a few seconds it jams so that I can remove all the clients but one (once a second) and still it does not recover.
Now while testing I got E.getErrorFlags: BUFFER_FULL before it got stuck
And at restart of the Espruino I got FIFO_FULL, but then it recovered.
In any error scenario I would like the node to restart, clear and continue to operate. How that could be done?
There are also many situations where the requests are not coming into the page handler at all. The EspruinoWifi server just sits there and does nothing while all the requests fail with timeout. It recovers when I upload the code and reset with the Web IDE when it is stuck it recovers.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
@Gordon Yes during the dump the clients failed to receive anything and wireshark showed only HTTP requests but not replies. I can reproduce the situation by first adding clients and in a few seconds it jams so that I can remove all the clients but one (once a second) and still it does not recover.
Now while testing I got E.getErrorFlags: BUFFER_FULL before it got stuck
And at restart of the Espruino I got FIFO_FULL, but then it recovered.
In any error scenario I would like the node to restart, clear and continue to operate. How that could be done?
There are also many situations where the requests are not coming into the page handler at all. The EspruinoWifi server just sits there and does nothing while all the requests fail with timeout. It recovers when I upload the code and reset with the Web IDE when it is stuck it recovers.