Sorry to hear that - that could be a sign that you're running low on memory as HTTPS can take a lot.
Do you think it's possible that maybe you're not closing the HTTPS connection, so it's staying open? So then multiple HTTPS connections open at the same time would chew through your RAM.
You could check process.memory().usage to see if the free memory is going down after each call, or if it's staying constant (which is what you want really)
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.
Sorry to hear that - that could be a sign that you're running low on memory as HTTPS can take a lot.
Do you think it's possible that maybe you're not closing the HTTPS connection, so it's staying open? So then multiple HTTPS connections open at the same time would chew through your RAM.
You could check
process.memory().usage
to see if the free memory is going down after each call, or if it's staying constant (which is what you want really)