crash:__CFRunLoopServiceMachPort.cold.1 :56

Question

Created Mar ’24

Replies 1

Boosts 0

Participants 2

After my project was packaged with Xcode15, the following crash occurred, which had not occurred before. After checking for a long time, the cause was not found, because similar problems did not occur when Xcode14 was used to package, so I think it is the problem caused by Xcode15 packaging

Incident Identifier: 3DFEAAAC-DCEE-4C6F-B51D-29BE9448A9C0
CrashReporter Key:   KSCrash2
Hardware Model:      iPhone15,3
Process:             KPlayi4Phone [11803]
Path:                /private/var/containers/Bundle/Application/FD3F5994-3F75-4477-B629-2343870A4995/KPlayi4Phone.app/KPlayi4Phone
Identifier:          com.KPlay.KPlay
Version:             2035752548 (11.0.73)
Code Type:           ARM-64
Parent Process:      ? [1]
Date/Time:           2024-03-28 15:02:18 +0800
Launch Time:         2024-03-28 15:02:10 +0800
OS Version:          iOS 16.2 (20C65)
Report Version:      104
Exception Type:  EXC_BREAKPOINT
Exception Codes: KERN_INVALID_ADDRESS at 0x00000001d256402c
Exception Subtype: SIGTRAP
Triggered by Thread:  0
Thread 0 Crashed:
0   CoreFoundation                  0x00000001d256402c __CFRunLoopServiceMachPort.cold.1 :56 (in CoreFoundation)
1   CoreFoundation                  0x00000001d242ebd4 __CFBasicHashIncSlotCount :0 (in CoreFoundation)
2   CoreFoundation                  0x00000001d242fd18 __CFRunLoopRun :1232 (in CoreFoundation)
3   CoreFoundation                  0x00000001d2434ec0 _CFRunLoopRunSpecific :612 (in CoreFoundation)
4   GraphicsServices                0x000000020c48b368 _GSEventRunModal :164 (in GraphicsServices)
5   UIKitCore                       0x00000001d492a86c -[UIApplication _run] :888 (in UIKitCore)
6   UIKitCore                       0x00000001d492a4d0 _UIApplicationMain :340 (in UIKitCore)
7   KPlayi4Phone                    0x0000000100f5608c main main.m:16 (in KPlayi4Phone)
8   ???                             0x00000001f0c56960 0x0000000000000000 + 8334436704
9   ???                             0x0000000000000000 0x0000000000000000 + 0

mycrash.crash

Boost

Answer 1

DTS Engineer OP

Apple

Apr ’24

Thanks for including the crash report. Sadly, it’s kinda munged, missing all the blank lines between sections. Did you post it as a file attachment, per the advice in Posting a Crash Report. If so, can you check the original file to see if the original file is similarly munged?

Also, is this an Apple crash report? It looks close, but there are things that aren’t quite right.

I’ll note that thread 3 suggests that you have your own crash reporter, which is something I specifically recommend against [1]. Try removing that and seeing if you get a better crash report.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

[1] For an explanation as to why, see Implementing Your Own Crash Reporter.

0