OS 2.7.1 Rev B persistent and random crashes (e0)

SDK Bug Reports
1

Sorry if this is the wrong place to post this.

I upgraded to 2.7.1 after seeing the prompt on my device and immediately began noticing crashes with code e0 while playing normally stable games, even navigating the device settings. Most reliably I can trigger a crash by checking for another system update, or trying to update my game library.

Noticing this trend of network related activity causing crashes, I am surprised to learn that this update was meant to correct issues with opening connections, though mine is rev b.

Things I've tried:

  • Factory reset
  • Reboot to recovery and re-update

All with no changes in behavior.

And now, seeing as there are issues with update for me, I thought I would just stay at 2.6.2 for the moment using recovery mode, but it appears I can't connect to the server to download games anymore, with the catalog giving me network error 12 after attempting to refresh. Edit: Also network error 12 when attempting to fetch a system update.

I've sent off several diagnostics reports of crashes, but I'm happy to upload logs here if that would be helpful.

Edit: I continued to troubleshoot but only made things worse, after another factory reset I'm now stuck at the register device screen with the same "server error". From the debug log:

query error line 1755,0: 12
Error fetching PIN:Internal Error: 12

Edit (04-27):
Server error appears to have been temporary and I'm back in, onboarding of course auto-updated to 2.7.1 and the crashes continue. I am at least able to provide logs again.

This was as I was trying to fetch my available games after re-linking the device:

crashlog.txt 1,8

--- crash at 2025/04/27 14:48:54---
build:208c5b3a-2.7.1-release.184449-buildbot
   r0:2408f1c9    r1:900ee610     r2:2001ada8    r3: 00000000
  r12:20010ecc    lr:2408f171     pc:24014150   psr: 210e0000
 cfsr:00000001  hfsr:00000000  mmfar:00000000  bfar: 00000000
rcccsr:00000000
heap allocated: 1281280
Lua totalbytes=128283237 GCdebt=-127574530 GCestimate=706553 stacksize=84

This was from a few minutes ago (13:34 PT at the time of writing) immediately after unlocking the device:

crashlog.txt 10,17

--- crash at 2025/04/27 20:25:28---
build:208c5b3a-2.7.1-release.184449-buildbot
   r0:2408f1c9    r1:9067f080     r2:2001ada8    r3: 00000000
  r12:906b2408    lr:2408f171     pc:24014150   psr: 21070000
 cfsr:00000001  hfsr:00000000  mmfar:00000000  bfar: 00000000
rcccsr:00000000
heap allocated: 9338688
Lua totalbytes=128485489 GCdebt=-127575225 GCestimate=884039 stacksize=42
2

I also get these random crashes when entering settings app. Crash log:

--- crash at 2025/04/27 20:48:03---
build:208c5b3a-2.7.1-release.184449-buildbot
   r0:00000001    r1:2403e675     r2:01000002    r3: 01000002
  r12:20010f2c    lr:2403e675     pc:2408f5da   psr: a10f0000
 cfsr:00008200  hfsr:40000000  mmfar:01000002  bfar: 01000002
rcccsr:00000000
heap allocated: 1154400
Lua totalbytes=128396335 GCdebt=-127574516 GCestimate=432104 stacksize=84

I can't tell if the crash is related to idle time or time of day. Like I can readily expect a crash if I am entering settings for the first time that day, but no crashes if I go into settings later that day.

I am running 2.7.1, but I also saw similar crashes from settings app while running 2.7.0. 2.6.2 was fine.

Edit: I don't get repeated crashes from entering settings app multiple times in the same day, but I do get a different crash (from a different address) when I try to refresh game list:

--- crash at 2025/04/27 21:05:59---
build:208c5b3a-2.7.1-release.184449-buildbot
   r0:2408f1c9    r1:9012db30     r2:2001ada8    r3: 00000000
  r12:00000000    lr:2408f171     pc:24014150   psr: 810e0000
 cfsr:00000001  hfsr:00000000  mmfar:00000000  bfar: 00000000
rcccsr:00000000
heap allocated: 1311296
Lua totalbytes=128289476 GCdebt=-127574522 GCestimate=713268 stacksize=84
3

What about Settings > Games? For me that's a pretty common one, about 50% of the time it'll crash after attempting to refresh for a few moments.

4

I just got that exact one (settings -> games), looks like the same address as yours.

1 Like
5

That jibes with what I'm seeing in the server logs--the crashes all show that it had run a background sync recently. It must not be cleaning up after itself correctly in that case. I'll see if I can reproduce that and get a fix in. Huge thanks for the info, both of y'all :slight_smile:

5 Likes
6

Have you noticed a pretty gnarly drop in battery? My last playdate would last many days maybe a week or more if I didn't play it. The refurbished one I just received on 2.7.1 is dying in like two days without use from a full charge.

7

I've only had mine for a couple weeks, less than that when this update rolled out, but I thought I might have noticed a pretty significant drop. Ever since I disconnected the WiFi it seems to avoid whatever is causing the crashes and apparently also draining the battery.

If you also experience crashes when unlocking the device, you may want to take a look at this thread and consider sharing your crashlog.txt.

8

I just found mine, where should I share it?

9

You can share it in the thread I linked in the previous reply, just to keep things organized. Also if you can remember the time of the crash it may be helpful to share so the timestamps of the crashes can be referenced by those looking into it, be sure to include your timezone. :slight_smile:

10

So far it seems like 2.7.2 addressed all of the issues I was experiencing. A huge thank you to everyone involved!

1 Like
11

I applied the 2.7.2 update after work today but my Playdate is still crashing. I suppose factory resetting the device would be futile?

12

I did notice that my download of Root Bear had stopped at 50% and that's when I noticed the crashing had started. Seeing that the bug was network related I disconnected from Wi-Fi and reconnected again - no crashes have been seen since. I'm definitely going to keep my eye on this, I'll post crash logs if it happens again.

1 Like
13

Well crud, the crashing is still happening. I sent a diagnostics report in but it's failing when I try to send in a crash report. Any idea what might be causing that?

14

You could try booting into recovery mode and reinstalling 2.7.2 from there. Also, if you're experiencing crashes on the new version it might be best to start a new thread to document it as this thread was specific to 2.7.1.