You are reading a single comment by @Gordon and its replies.
Click here to read the full conversation.
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
Well, it's because there are still open HTTP connections - However I don't know whether that is because the server isn't closing the connection, or because somehow Espruino isn't responding to what the ESP8266 says.
What happens if you check the memory usage one minute later? If it's lower then it may well be that the server isn't closing the connection.
And you're not getting any errors reported? I guess you could use the
wifi.at.debug()to see if the ESP8266 really is reporting that the connections are closed.Does
res.on('close',always end up getting called for every HTTP request? If it is and the request still isn't closed then there's some bigger issue.