CPU load during HTTP response can get sockets stuck

+Gordon I think this might be related to the full FIFO buffer. Especially with the v0.50 AT firmware, I think the init string is longer than with v0.40.

If I wait for my initial wifi.startAP to fail, and then send an AT command directly, the buffer seems to be full of junk. If I send the AT command again, everything clears up:

Uncaught No 'ready' after AT+RST
wifi.at.cmd('AT\r\n', 1000, console.log);
=undefined
rllrcânlìb|ìpìlbónolnobbpblslpónàlcoââob|~ònîllonAT
wifi.at.cmd('AT\r\n', 1000, console.log);
=undefined
AT