Ah, OK. Is this when you select the save data slot or when you are booting the game?
I have just uploaded a patched version which fixes a crash bug which can occur under some circumstances when you transition between the save select to the main menu. Not sure if this is the one you are encountering here or not, though.
Hiya,
Thanks for responding - I appreciate it, as I don't particularly want anyone to have a bad time with this.
That said - I have to admit I'm completely baffled by this one. There's not a huge difference between the games first boot and restarting it, mostly just the first time you start it creates a header file for each of the save slots, then checks for any completed stage files so that it can total up the number of collected coins. I'm guessing it's not going to be the 10 second "I think your game is stuck in a loop" Playdate OS crash.
Does the game still crash when restarting if you exit without having created a save file?
Does the game still crash when restarting if you exit immediately after entering your name (whilst the opening sequence is still playing), or is it only if you have played a stage or two first?
I've uploaded a second version of the game labelled as Debug above - if you have time (no pressure - don't really want to put anyone out) could you give that a try a tell me if it's still crashing and reporting an error or not? I've moved some of the initialisation code in the hopes that it may report a proper error message if things aren't being done at boot time.
Here is a data dump when it crashed. Downloaded debug fix, still crashing
- watchdog reset at 2023/10/03 16:00:17---
build:1fd086bf5715-2.0.3-release.158184-buildbot
r0:00000000 r1:00000000 r2:00030cee r3: 00000000
r12:006d3000 lr:080353ef pc:080350fa psr: 61000000
rcccsr:00000000
heap allocated: 7345024
Lua totalbytes=128164686 GCdebt=-127560163 GCestimate=589398 stacksize=84
--- watchdog reset at 2023/10/03 16:00:53---
build:1fd086bf5715-2.0.3-release.158184-buildbot
r0:40012c00 r1:00001f40 r2:06422c15 r3: 00082800
r12:006d3000 lr:0803c615 pc:0803c444 psr: 21000000
rcccsr:00000000
heap allocated: 3123968
Lua totalbytes=822800 GCdebt=-240416 GCestimate=411477 stacksize=80
--- crash at 2023/10/03 16:05:09---
build:1fd086bf5715-2.0.3-release.158184-buildbot
r0:00000000 r1:0803e0d3 r2:20010220 r3: 00000000
r12:006d3000 lr:0803e0d3 pc:08042a9e psr: 61000000
cfsr:00020000 hfsr:40000000 mmfar:00000000 bfar: 00000000
rcccsr:00000000
heap allocated: 0
Lua totalbytes=0 GCdebt=0 GCestimate=0 stacksize=0
Hope this helps Don't understand any of this
I'm a little stumped on this at this point, unfortunately. I appreciate you giving that a try.
I'll need to have a think about it - it seems to only be effecting some users, which is absolutely the worst kind of bug to figure out because it's possibly only going to happen on their devices. There's a few things I can maybe do to reduce the amount of garbage generated whilst initialising the title screen that I can give a try, but that's going to take a while to look at and may not fix the issue.
Sorry that's not a super-useful response, but this just has me baffled at this point.
