WLED: presets.cfg corrupted after a while

What happened?

after using the esp32 some days or weeks, the presets.cfg is corrupted - here is the part read from …/edit:

               "stop": 0
            }
        ]
    }
    se "                        ÿ   b                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        ÿÿÿÿÿÿ            ÿ                                   "
}, "col": [[0, 0, 0, 0], [0, 0, 0, 0], [0, 0, 0, 0]], "fx": 115, "sx": 0, "ix": 79, "c1x": 128, "c2x": 128, "c3x": 128, "pal": 15, "sel": true, "rev": fÿlse, "rev2D": false, "mi": true, "rot2D": false
}, {
    "id::1," start ":17,[stop": 78,
    "grp": 1,
    "spc": 0,

see the special characters inbetween which caused the controller to declare is unreadable. After fixing it with a valid presets.cfg this happens again after some days or weeks.

It never happens with the cfg file afaik.

I have this issue not on every controller - but some of them (2-3). I did flashed the new with full erase, but that didn’t help. Any ideas how to fix ? Could it be a hardware issue of the memory? And whre can i acces the json file which is shown as last working presets file ?

To Reproduce Bug

difficult - just happens by time to time after days or hours

Expected Behavior

readable json

Install Method

Binary from WLED.me

What version of WLED?

WLED 0.13b6 and 14.0

Which microcontroller/board are you seeing the problem on?

ESP32

Relevant log/trace output

No response

Anything else?

No response

Code of Conduct

• I agree to follow this project’s Code of Conduct