Assistance solving longlived crash

Question

Created Jun ’19

Replies 1

Boosts 0

Participants 2

Hello, I would appreciate any assistance that could help me track down this crash. This crash is extremely common in my application.

Does this crash happen when players suspend the application?
It seems as many players don't experience this crash (as there are no complaints despite common enough so that every user should experience it).

Any help is greatly appreciated.

Incident Identifier: 3AAB7482-75A9-457D-AE76-71A0ADDB1723
CrashReporter Key:   3909a85f0d0d66ed605d7f83eb61239243425734
Hardware Model:      iPad6,11
Process:             myApp [937]
Path:                /private/var/containers/Bundle/Application/759863FC-74B9-4F40-8E85-67E292DF1413/myApp.app/myApp
Identifier:          com.eldring.myApp
Version:             1.1.1 (1.1.1)
Code Type:           ARM-64 (Native)
Role:                Non UI
Parent Process:      launchd [1]
Coalition:           com.eldring.myApp [540]
Date/Time:           2019-01-14 00:49:09.8112 -0500
Launch Time:         2019-01-14 00:28:12.2806 -0500
OS Version:          iPhone OS 10.3.2 (14F90)
Report Version:      104
Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000350
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]
Triggered by Thread:  0
Thread 0 name:
Thread 0 Crashed:
0   myApp                  0x000000010055f0c4 0x100010000 + 5566660
1   myApp                  0x000000010008f858 0x100010000 + 522328
2   myApp                  0x000000010008f858 0x100010000 + 522328
3   myApp                  0x0000000100092400 0x100010000 + 533504
4   myApp                  0x0000000100091c58 0x100010000 + 531544
5   myApp                  0x00000001000925b0 0x100010000 + 533936
6   myApp                  0x000000010057ff6c 0x100010000 + 5701484
7   myApp                  0x000000010057bbb4 0x100010000 + 5684148
8   myApp                  0x000000010057bf3c 0x100010000 + 5685052
9   myApp                  0x000000010057a9b0 0x100010000 + 5679536
10  myApp                  0x00000001000214dc 0x100010000 + 70876
11  myApp                  0x0000000100021ae0 0x100010000 + 72416
12  myApp                  0x0000000100028fd8 0x100010000 + 102360
13  UIKit                           0x000000018edc3c70 -[UIApplication _terminateWithStatus:] + 244 (UIApplication.m:6179)
14  UIKit                           0x000000018efc21a0 __102-[UIApplication _handleApplicationDeactivationWithScene:shouldForceExit:transitionContext:completion:]_block_invoke.2093 + 792 (UIApplication.m:6492)
15  UIKit                           0x000000018efc5950 _runAfterCACommitDeferredBlocks + 292 (UIApplication.m:2469)
16  UIKit                           0x000000018efb79ec _cleanUpAfterCAFlushAndRunDeferredBlocks + 528 (UIApplication.m:2447)
17  UIKit                           0x000000018ed2b648 _afterCACommitHandler + 132 (UIApplication.m:2499)
18  CoreFoundation                  0x0000000188bbc9a8 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 32 (CFRunLoop.c:1802)
19  CoreFoundation                  0x0000000188bba630 __CFRunLoopDoObservers + 372 (CFRunLoop.c:1898)
20  CoreFoundation                  0x0000000188bbaa7c __CFRunLoopRun + 956 (CFRunLoop.c:2849)
21  CoreFoundation                  0x0000000188aeada4 CFRunLoopRunSpecific + 424 (CFRunLoop.c:3113)
22  GraphicsServices                0x000000018a554074 GSEventRunModal + 100 (GSEvent.c:2245)
23  UIKit                           0x000000018ed9e058 UIApplicationMain + 208 (UIApplication.m:4089)
24  myApp                  0x000000010010fffc 0x100010000 + 1048572
25  libdyld.dylib                   0x0000000187af959c start + 4

Boost

Answer 1

DTS Engineer OP

Apple

Jun ’19

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)  
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000350

This indicates that your app has crashed by it accessed unmapped memory. The address, 0x0000000000000350, is way down in low memory, suggesting that this is a

NULL

pointer dereference.

The crashing code has this backtrace:

Thread 0 Crashed:  
0   myApp … 0x100010000 + 5566660  
1   myApp … 0x100010000 + 522328  
2   myApp … 0x100010000 + 522328  
3   myApp … 0x100010000 + 533504  
4   myApp … 0x100010000 + 531544  
5   myApp … 0x100010000 + 533936  
6   myApp … 0x100010000 + 5701484  
7   myApp … 0x100010000 + 5684148  
8   myApp … 0x100010000 + 5685052  
9   myApp … 0x100010000 + 5679536  
10  myApp … 0x100010000 + 70876  
11  myApp … 0x100010000 + 72416  
12  myApp … 0x100010000 + 102360  
13  UIKit … -[UIApplication _terminateWithStatus:] + 244 (UIApplication.m:6179)  
…

Frame 13 indicates that UIKit is trying to terminate your app, probably via the

-applicationWillTerminate

app delegate callback. Frames 12 through 0 are your code, and to understand this further you’ll need to symbolicate the crash report. See Technote 2151 Understanding and Analyzing iOS Application Crash Reports for more information about symbolication.

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

0