Espruino Pico webserver

@ClearMemory041063 it'd be good if you could find a way to reproduce this?

Since there can only be 5 sockets (#0..#4), Espruino's driver uses socket #5 to represent the server. It might be that the 0.60 firmware supports more sockets and so hits #5, which makes Espruino try and do server-related stuff?

@samppa so that dump was during the point at which it wasn't responding? It looks like Espruino is working perfectly, so it's on the ESP8266 side.

Could you try:

// connected
wifi.at.cmd("AT+CIPSTO=2\r\n",1000,function(d) {
  print(d);
  // start server, do other stuff here
});

That sets the server timeout. It's never been an issue before, but it might allow the server to drop connections where nothing happens for 2 seconds, which should hopefully aid speedy recovery.