You are reading a single comment by @Gordon and its replies.
Click here to read the full conversation.
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.
@Gordon
Ok - is this the first time it's happened to you since upgrading to (or past) 2v12?
Someone else posted up basically the exact same thing last week.
Basically: 2v11 had a bug where if the flash storage got corrupted (and it happened to be arranged in a certain way) then some flash memory wasn't erased that should have been.
2v12 fixed that, but if your storage already had that bit of unerased memory in it from the 2v11 bug, as storage gets more and more full you'll eventually hit that unerased data, everything gets corrupted, and you'll see the problem you had.
But hopefully now Storage has been completely erased - properly - you won't see the problem again