Is that trace from when it has the memory leak? I don't see anything obvious in there (but it's hard to see!) - although E.getSizeOf is definitely getting pretty confused by the references back in the functions.
Perhaps outputting the data from trace() (without the Serial4) before and after the memory leak might help, as we could then diff them.
Also, do you get the memory leak with non-"compiled" code? It could be it's a memory leak in the interpreter caused by a bug in the compiler.
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.
Is that trace from when it has the memory leak? I don't see anything obvious in there (but it's hard to see!) - although
E.getSizeOf
is definitely getting pretty confused by the references back in the functions.Perhaps outputting the data from
trace()
(without the Serial4) before and after the memory leak might help, as we could then diff them.Also, do you get the memory leak with non-
"compiled"
code? It could be it's a memory leak in the interpreter caused by a bug in the compiler.