Crash in background on iOS 15 EXC_CRASH (SIGKILL)

Question

Created Nov ’21

Replies 31

Boosts 0

Views 24k

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.

Boost

Answer 1

MingXiao OP

Feb ’22

Hi edford,

Has several SIGKILL crash reports with no Termination Reason.

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

Thanks!

0

Answer 2

awaisfayyaz17.apple OP

Mar ’22

@edford: I appreciate your contribution to this thread. I encountered a similar situation. When I downloaded the crash reports from TestFlight, there was no 'reason' field. Then I read all the replies and your comments and found that I needed to check the crash reports using the XCode crashers organizer.

I am highlighting this for future readers:

To find the 'reason' field, It is important that you analyze the crash using XCode crashes organizer. Find your crash in the organizer, right-click and then click 'show in finder. This will be an XCcrashPoint file. Open it and the reason field should be there. See attached screenshot

Hope it helps.

Awais

0

Answer 3

awaisfayyaz17.apple OP

Mar ’22

@edford.

I am attaching my recent crash report as an attachment here. I have anlysed the crash report and i believe my app was stuck in some kind of deadlock. I am using locks to manager synchronization. Can you please spare some minutes and verify that my assumption is correct.

Bundle of thanks.

front-board.crash

0

Answer 4

Daveinthehat OP

Apr ’22

We continue to have problems determine the root cause of Intermittant APP crash. We were told to look at the Third Party SDK that opens and closes the Lidar camera. We have confirmed we are opening and closing the camera properly. We built a test app to open and close the app and it ran 150 times without a problem.

Could a thread that saves the JPG pictures as a video cause the sensor_stream to hang and crash the app? Here is snippets of the crash logs. Any further help would be appreciated.

Crash Log1 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000134500000 Thread 46 name: Thread 46 Crashed: 0 libsystem_platform.dylib 0x00000001f110da84 _platform_memmove + 52 1 UnityFramework 0x0000000107c4eb60 Sensor_Stream_mFF850E96E26ADC438DFA62EFFABFDAEDE3B6DEEC + 632 (LightBuzz.BodyTracking.cpp:24277)

Crash Log2 Triggered by Thread: 56. Kernel Triage: VM - pmap_enter failed with resource shortage Thread 56 name: Thread 56 Crashed: 0 libsystem_platform.dylib 0x00000001f110da84 _platform_memmove + 52 1 UnityFramework 0x0000000109362b58 Sensor_Stream_mFF850E96E26ADC438DFA62EFFABFDAEDE3B6DEEC + 632 (LightBuzz.BodyTracking.cpp:24277)

crashlog.crash

0

Answer 5

4cv1_ OP

Aug ’22

Hi 👋! He tried to solve this situation. Any clue would be greatly appreciated.

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

0

Answer 6

gharary OP

Oct ’22

@edford, I have also faced this issue and filed the report here: Feedback. Can you take a look at this one too, please?

0