Termination Reason: FRONTBOARD 2343432205

Question

vsandeepraju OP

Created May ’22

Replies 2

Boosts 0

Views 4.6k

Participants 3

We are seeing UI stuck for our app and could see the below information in the analytics log

Exception Type:  EXC_BAD_ACCESS (SIGKILL)
Exception Subtype: KERN_PROTECTION_FAILURE at 0x000000016f5d3ff0
Exception Codes: 0x0000000000000002, 0x000000016f5d3ff0
VM Region Info: 0x16f5d3ff0 is in 0x16f5d0000-0x16f5d4000;  bytes after start: 16368  bytes before end: 15
      REGION TYPE                 START - END      [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      MALLOC_LARGE             164100000-164180000 [  512K] rw-/rwx SM=PRV  
      GAP OF 0xb450000 BYTES
--->  STACK GUARD              16f5d0000-16f5d4000 [   16K] ---/rwx SM=NUL  ... for thread 0
      Stack                    16f5d4000-16f6d0000 [ 1008K] rw-/rwx SM=PRV  thread 0
Exception Note:  EXC_CORPSE_NOTIFY
Termination Reason: FRONTBOARD 2343432205 
<RBSTerminateContext| domain:10 code:0x8BADF00D explanation:scene-update watchdog transgression: application<***.xxxx.xxxx>:522 exhausted real (wall clock) time allowance of 10.00 seconds
ProcessVisibility: Background
ProcessState: Running
WatchdogEvent: scene-update
WatchdogVisibility: Background
WatchdogCPUStatistics: (
"Elapsed total CPU time (seconds): 18.690 (user 7.330, system 11.360), 28% CPU",
"Elapsed application CPU time (seconds): 10.987, 17% CPU"
) reportType:CrashLog maxTerminationResistance:Interactive>

Triggered by Thread:  0

I cannot find any information on the Termination Reason that can help me to understand the issue

Attaching the Analytics log for your reference...

Analytics Log.crash

Boost

Answer 1

DTS Engineer OP

Apple

May ’22

Consider this:

code:0x8BADF00D

This leads straight to Addressing Watchdog Terminations.

Having said that, your main thread backtrace looks like this:

Thread 0 Crashed::   Dispatch queue: com.apple.main-thread
…
500  My_App                        	       0x100e6fd06
501  My_App                        	       0x100e6fc6a
502  My_App                        	       0x100e6f162
503  My_App                        	       0x100e6fd06
504  My_App                        	       0x100e6fc6a
505  My_App                        	       0x100e6f162
506  My_App                        	       0x100e6fd06
507  My_App                        	       0x100e6fc6a
508  My_App                        	       0x100e6f162
509  My_App                        	       0x100e6fd06
510  My_App                        	       0x100e6fc6c

Two things to note here:

It ends at frame 510, which is where the crash reporter gives up.
There’s a loop — note that frame 509 is the same as 506 is the same as 503 — suggesting that you’re suffering from infinite recursive death or, more likely, stack corruption that’s actually looped the frame pointers.

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

0

Answer 2

xidipeng OP

Jul ’22

me too, crash in ios 15.5

0