Triggered by Thread: 0
Thread 0 Crashed: 0 dyld 0x1a87922b0 lsl::PreallocatedAllocatorLayout<278528ull>::init(char const**, char const**, void*) + 436 1 dyld 0x1a878ba38 start + 1960
Thread 0 crashed with ARM Thread State (64-bit): x0: 0x2010003030100000 x1: 0x0000000fffffc0d0 x2: 0x0000000000000004 x3: 0x00000001a87607a9 x4: 0x0000000000000000 x5: 0x0000000000000000 x6: 0x0000000000000000 x7: 0x0000000000000000 x8: 0x2010003030100000 x9: 0x2010003030100000 x10: 0x000000016d923dfd x11: 0x00000001a87ccf30 x12: 0x0000000000000050 x13: 0x0000000000000044 x14: 0x0000000000052010 x15: 0x0000000000000000 x16: 0x0000000000000000 x17: 0x0000000000000000 x18: 0x0000000000000000 x19: 0x00000001801d0000 x20: 0x000000016d923b50 x21: 0x000000016d923af8 x22: 0x00000001e6184050 x23: 0x000000016d9237d8 x24: 0x0000000fffffc10c x25: 0x0000000000000000 x26: 0x0000000000000000 x27: 0x0000000000000000 x28: 0x0000000000000000 fp: 0x000000016d923870 lr: 0xb0228001a8792130 sp: 0x000000016d9237d0 pc: 0x00000001a87922b0 cpsr: 0x60001000 far: 0x00000001e61840e0 esr: 0x92000047 (Data Abort) byte write Translation fault
Binary Images: 0x1a8758000 - 0x1a87db693 dyld arm64e <77c1eed22ed7396aba34e770120d81d4> /usr/lib/dyld 0x1024dc000 - 0x10594ffff main_executable_path_missing arm64 <b4af5d3d511d3f9e8b5a66245101c348> /main_executable_path_missing 0x0 - 0xffffffffffffffff ??? unknown-arch <00000000000000000000000000000000> ???
Error Formulating Crash Report: dyld_process_snapshot_get_shared_cache failed
EOF
App crashes at every run, both AppStore users and running from Xcode debug mode.
Restarting the phone worked, but not ideal for real users... Is this a known issue?
Yes, but it's a bit more complicated than that. The kernel team is aware of the issue and has actually been investigating it for awhile but they still don't really know what the problem actually is. The actual failure is rare enough that we've never been able to directly reproduce the issue and diagnostic data we have gotten doesn't really make very much sense. Here's what I can say at this point:
- There isn't any indication that the problem is specifically tied to the app itself or anything your app "did". Note the reason you see "main_executable_path_missing" is that dyld hasn't actually gotten far enough into the loading process that it's actually started interacting with your specific executable:
0x104784000 - 0x104790000 main_executable_path_missing arm64 <d6c015912aa137f38accbdda1c1671f0> /main_executable_path_missing
-
The issue appears to be tied to some kind of transient state, so it's expected that rebooting will resolve the issue.
-
The issue has been very difficult to reproduce and it's still very unclear what factors are able to trigger it.
With an issue like this I'd typically recommend that you file bugs, however, I'm not sure that would help much here. The issue is low level enough that an post-reboot sysdiagnose isn't useful and transient that it's trying to catch it "again" isn't all that useful. Lastly, the issue is low level enough that it's not clear that any sysdiagnose would be also that useful. The team has made some changes in iOS 18.1 to try and get better data (not this this may cause the "same" crash to generate a slightly different crash log), but individual reports on specific failures are unlikely to help much.
However, the one exception to this is if you're able to reliably reproduce the issue (after rebooting the device), particularly if you're able to reproduce the issue across devices. If you have any specific information about what might be triggering the bug, then please file a bug on that and post the bug number here.
__
Kevin Elliott
DTS Engineer, CoreOS/Hardware
