I had a look and also found E.on('errorFlag', function(errorFlags) { ... }); Was thinking there might be a way of dumping a stacktrace to work out what prompted the MEMORY_BUSY, but then realised that the context would be lost by the time E.on('errorFlag',) has been received.
I see MEMORY_BUSY every now and again when running my Pastel clock. As far as I know I am not doing anything particularly heavy etc. Could this be caused by code that might cause a memory leak (I dont think Pastel has a Memory leak), just cluthing at straws 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.
I had a look and also found
E.on('errorFlag', function(errorFlags) { ... });
Was thinking there might be a way of dumping a stacktrace to work out what prompted theMEMORY_BUSY
, but then realised that the context would be lost by the time E.on('errorFlag',) has been received.I see
MEMORY_BUSY
every now and again when running my Pastel clock. As far as I know I am not doing anything particularly heavy etc. Could this be caused by code that might cause a memory leak (I dont think Pastel has a Memory leak), just cluthing at straws really.