Ouch - thanks for letting me know, I'll check into it.
Is there any other code running on the device, or is it literally just what you have above? And are you running on 1v94, or one of the 'latest' builds for Puck.js?
MEMORY_BUSY can occur when something happens in an IRQ that needs variables while the device is doing garbage collection in the main loop. Usually that's rare, but when memory runs low it can cause GC passes to fire more often, which could be making it happen far more frequently.
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.
Ouch - thanks for letting me know, I'll check into it.
Is there any other code running on the device, or is it literally just what you have above? And are you running on 1v94, or one of the 'latest' builds for Puck.js?
MEMORY_BUSY can occur when something happens in an IRQ that needs variables while the device is doing garbage collection in the main loop. Usually that's rare, but when memory runs low it can cause GC passes to fire more often, which could be making it happen far more frequently.