Same result... It's interesting that if I run it and don't connect at all, the system stays up a LONG time. Recent tests show that after a connection/close, 305 seconds/counts later (with a little stall at a count of 300), the Arduino locks up. 3 times in a row now it has crashed right at that count. It's like something is causing a stack overflow or similar after a number of loop iterations, but only after a connect & close.
The only code it would be consistently running in those iterations would be: WiFiClient client = server.available();
But it runs that even before there's a connection at all and seems to stay up fine. It shouldn't be trying to create new instances?
Thoughts? Any chance you could run the code on your side and see if you get a lockup as well after a connect/close? Maybe there's a ghost in my machine...
Thanks.