Crash in background on iOS 15 EXC_CRASH (SIGKILL)

App & System Services Core OS
SebC99 OP
Created Nov ’21
Replies 31
Boosts 0
Views 26k
Participants 33

Hello, Since the first iOS 15 beta and even with all the next public releases, we have a very weird crash each time our app enters background. The crash logs don't help at all unfortunately

Each time we see:

Exception Type:  EXC_CRASH (SIGKILL)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note:  EXC_CORPSE_NOTIFY
Triggered by Thread:  0

and

Thread 0 name:
Thread 0 Crashed:
0   libsystem_kernel.dylib        	0x00000001b7a08564 mach_msg_trap + 8
1   libsystem_kernel.dylib        	0x00000001b7a08bfc mach_msg + 76 (mach_msg.c:119)
2   CoreFoundation                	0x0000000181089698 __CFRunLoopServiceMachPort + 372 (CFRunLoop.c:2646)
3   CoreFoundation                	0x000000018108d98c __CFRunLoopRun + 1212 (CFRunLoop.c:3000)
4   CoreFoundation                	0x00000001810a13c8 CFRunLoopRunSpecific + 600 (CFRunLoop.c:3268)
5   GraphicsServices              	0x000000019c8b238c GSEventRunModal + 164 (GSEvent.c:2200)
6   UIKitCore                     	0x0000000183a47060 -[UIApplication _run] + 1100 (UIApplication.m:3457)
7   UIKitCore                     	0x00000001837c4b8c UIApplicationMain + 2124 (UIApplication.m:5013)

And sometimes we have:

Kernel Triage:
VM - Compressor failed a blocking pager_get

or

Kernel Triage:
VM - pmap_enter failed with resource shortage
VM - Compressor failed a blocking pager_get

But no other info. We can't reproduce it on simulators or on real devices with non-production release (linked to Xcode). But the crashes are here each time we build a release version.

Any help would be appreciated!

NB: it seems similar to this one but we are not even sure

2021-11-01_00-13-03.9761_+0100-a5388bfdcea65316d79dc2c3a4ac95ad146c2cb3.crash
Answered by DTS Engineer in 703406022

Many of you in this thread have opened bug reports in Feedback Assistant — thank you for filing those to help us address this! We have deployed a fix to the backend services that provide crashes for your app into the Xcode Organizer, so if you receive EXC_CRASH (SIGKILL) crash reports from now on through the Organizer, those reports should be attributed with an exception code to explain why the system terminated your app.

If you still see any reports without the exception code, please post the complete crash report to this thread using the attachment feature so we can verify that the code is still missing.

Replies  31
Boosts  0
Views  26k
Participants  33
DTS Engineer OP
Apple
Nov ’21

How did you acquire this crash? A system termination (i.e. a SIGKILL initiated by the system) should have an additional reason code or description of the reason behind the termination.

0
SebC99 OP
Nov ’21

I found a new one with the following reason: Termination Reason: RUNNINGBOARD 3735883980 (equivalent of 0xdead10cc)

0
marencod OP
Nov ’21

i had a similar problem

was related to an old version of Realm

1
ryotrix OP
Nov ’21

I have a totally same crash and Kernel Triage: VM - Compressor failed a blocking pager_get

Crash Memory Stack below:

Thread 0 name: Thread 0 Crashed: 0 libsystem_kernel.dylib 0x00000001b7a08564 mach_msg_trap + 8 1 libsystem_kernel.dylib 0x00000001b7a08bfc mach_msg + 76 (mach_msg.c:119) 2 CoreFoundation 0x0000000181089698 __CFRunLoopServiceMachPort + 372 (CFRunLoop.c:2646) 3 CoreFoundation 0x000000018108d98c __CFRunLoopRun + 1212 (CFRunLoop.c:3000) 4 CoreFoundation 0x00000001810a13c8 CFRunLoopRunSpecific + 600 (CFRunLoop.c:3268) 5 GraphicsServices 0x000000019c8b238c GSEventRunModal + 164 (GSEvent.c:2200) 6 UIKitCore 0x0000000183a47060 -[UIApplication _run] + 1100 (UIApplication.m:3457) 7 UIKitCore 0x00000001837c4b8c UIApplicationMain + 2124 (UIApplication.m:5013)

More information: hardware: iPhone XR iOS version: 15.0.2 (19A404)

waiting for any resolution and hoping this could be resolved asap.

0
DTS Engineer OP
Apple
Nov ’21

For anyone receiving a system termination (i.e. a Exception Type: EXC_CRASH (SIGKILL)) and also seeing 0x0 in the Exception Codes line, the system should have output additional information useful for diagnosing the reason the system terminated the app, such as the exception codes 0x8badf00d, 0xdead10cc, or 0xbaadca11, as documented in Understanding the Exception Types in a Crash Report.

Please open a bug report using Feedback Assistant, as this information should never be missing from the crash report, and is crucial for identifying the source of the problem. In your bug report, please include the full Apple crash report (no reports from third-party crash reporters), as well as a description of how you received the crash report, such as through the Xcode Crashes Organizer. Once you have filed the bug report, please post the FB number here.

2
algrid OP
Nov ’21

I also have a crash report that looks almost exactly the same. More than that, I have two more different crash reports, but all of them have zero Exception Codes and have no "Termination Reason" field.

In my case in all those crash reports I have a ton of threads that are waiting for some network operations (some Firestore stuff in my app) so my guess is that it can be related to some resource shortage (memory? descriptors? something related to threading?). But that's just a guess, I may very well be wrong.

0
Dmytro Yunchyk OP
Nov ’21

Since first iOS 15 build we've got a lot of the same crashes. We believe iOS 15 has some regressions. There are too many EXC_CRASH (SIGKILL) without any visible reason.

1
Rumio OP
Dec ’21

@edford, I can confirm seeing crash reports with 0x0 exception codes on iOS 15. My guess it is the watchdog killing the app, but I'm not sure. Please see FB9791707.

0
IAmMichellis OP
Dec ’21

@edford I am also seeing crash reports with 0x0 exception codes. I have a suspicion a thread other than main is the real culprit, but there's no evidence of that in the report. Please see FB9801972.

0
x010044 OP
Dec ’21

I'm also experiencing the same issue, with limited knowledge, and only in iOS 15.

Exception Type: EXC_CRASH (SIGKILL) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Triggered by Thread: 0

Kernel Triage: VM - Compressor failed a blocking pager_get

Thread 0 name: Thread 0 Crashed: 0 libsystem_kernel.dylib 0x00000001ba77b5a0 semaphore_wait_trap + 8 1 libdispatch.dylib 0x0000000183b05ee0 _dispatch_sema4_wait + 28 (lock.c:139) 2 libdispatch.dylib 0x0000000183b06598 _dispatch_semaphore_wait_slow + 132 (semaphore.c:132)

Also reported this in the Feedback Assistant: FB9803928

0
haisk OP
Dec ’21

@edford please take a look at my report https://feedbackassistant.apple.com/feedback/9809233

Look like something is wrong with App Group.

0
lei OP
Dec ’21

@edford please take a look at my report https://feedbackassistant.apple.com/feedback/9816327 I get these crash logs from Xcode organizer. All of them have no crash reason and organizer shows NO_CRASH_STACK + 0 for them.

0
PostChris OP
Dec ’21

hi @edford, I'm having a similar issue. Filed a report here https://feedbackassistant.apple.com/feedback/9823992. Thanks

0
Alex_Garcia_87 OP
Dec ’21

Hi @edford,

I’m also seen SIGKILL crashes with 0x0 exception codes and no termination reason. In this case, looking at the backtraces, it seems that it is originated from core data / cloudkit.

https://feedbackassistant.apple.com/feedback/9825704

Thanks!

0
chojubo OP
Jan ’22

Hello edford,

As advised I've submitted a bug report here with the details you requested: https://feedbackassistant.apple.com/feedback/9831706

In my case, I have 5 crashes which are all Exception Type: EXC_CRASH (SIGKILL), and with missing "Termination Reason".

The Kernel Triage: sections include variations on the following:

VM - Compressor failed a blocking pager_get
VM - Fault hit memory shortage
0
Crash in background on iOS 15 EXC_CRASH (SIGKILL)
First post date Last post date
 
 
Q