See edit at foot of this post... not sure if this is a bug but same in 1.87 when I replicate the process.
There is a regression in that build, a memory leak, maybe Wifi or socket related? I don't know at what point it may have been introduced, since I'm on 1.87, but there's a steady reduction in process.memory().free when I review. Reverting to 1.87 and stable again.
Edit: Actually, you only get this on saving code, and in 1.87 too. Upload the code, let it start running, save() in the console on left, and then free starts to decline. Maybe this is not an issue since I only did this for the purpose of the test above.
Normally, code will be wrapped by E.on("init", ...) at upload before save().
Am interested to know what could be happening here though
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.
See edit at foot of this post... not sure if this is a bug but same in 1.87 when I replicate the process.
There is a regression in that build, a memory leak, maybe Wifi or socket related? I don't know at what point it may have been introduced, since I'm on 1.87, but there's a steady reduction in
process.memory().free
when I review. Reverting to 1.87 and stable again.The sample code I tried.
Edit: Actually, you only get this on saving code, and in 1.87 too. Upload the code, let it start running,
save()
in the console on left, and then free starts to decline. Maybe this is not an issue since I only did this for the purpose of the test above.Normally, code will be wrapped by
E.on("init", ...)
at upload beforesave()
.Am interested to know what could be happening here though