iOS simulator crashes Termination Reason: FRONTBOARD 2343432205 0x8BADF00D

Avatar
Nynke Van Der Heide
Created

Hello,

My app often crashes when I use iOS simulators. I would like some help with reading the crash report that is generated. Especially with the part below Thread 0 Crashed. Based on other posts I understand that the 0x8BADF00D in the crash report is a WatchDog crash that basically says that WatchDog terminated the app because the main thread was blocked for a significant time. Many processes can block the main thread so it's hard to find out what it is in our specific case. Can someone help me reading through the crash report?      

Background information The application is Xamarin Native and I use Rider as an IDE. When I use Visual Studio, the simulators run just fine. No crash occurs while using my app on a device.

The crash happens on multiple simulators with different OS versions. I already deleted XCode cache, erased content and settings of several simulators and deleted iOS DeviceSupport files.

Crash report

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Incident Identifier: 24DBB87B-F450-49C2-8F1B-CCCC974EF42A
CrashReporter Key:   B8EF2F41-EF9C-6D5A-7C3B-07BAA6A9971D
Hardware Model:      MacBookPro16,1
Process:             ###.iOS [27855]
Path:                /Users/USER/Library/Developer/CoreSimulator/Devices/#####/data/Containers/Bundle/Application/###/XXX.iOS.app/XXX.iOS
Identifier:          #######
Version:             5.1.1 (5962)
Code Type:           X86-64 (Native)
Role:                Foreground
Parent Process:      launchd_sim [25534]
Coalition:           com.apple.CoreSimulator.SimDevice.A5D0C88E-0242-4F59-A41A-C2996FABCCF7 [14325]
Responsible Process: SimulatorTrampoline [6434]

Date/Time:           2024-07-15 15:53:08.7859 +0200
Launch Time:         2024-07-15 15:49:17.5017 +0200
OS Version:          macOS 14.5 (23F79)
Release Type:        User
Report Version:      104

Exception Type:  EXC_CRASH (SIGKILL)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: FRONTBOARD 2343432205 
<RBSTerminateContext| domain:10 code:0x8BADF00D explanation:[application<com.#####>:27855] failed to terminate gracefully after 5.0s
ProcessVisibility: Unknown
ProcessState: Running
WatchdogEvent: process-exit 
WatchdogVisibility: Background
WatchdogCPUStatistics: (
"Elapsed total CPU time (seconds): 4.450 (user 2.690, system 1.760), 5% CPU",
"Elapsed application CPU time (seconds): 0.001, 0% CPU"
) reportType:CrashLog maxTerminationResistance:Interactive>

Triggered by Thread:  0

Kernel Triage:
VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter
VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter
VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter
VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter
VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter


Thread 0 Crashed:: tid_103 Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib                0x7fff7016f44a writev + 10
1   libsystem_trace.dylib                 0x7fff200525db _os_trace_writev + 84
2   libsystem_trace.dylib                 0x7fff20050493 _os_log_impl_mirror_to_stderr + 622
3   libsystem_trace.dylib                 0x7fff2004fba3 _os_log_impl_flatten_and_send + 8588
4   libsystem_trace.dylib                 0x7fff20051252 _os_log_with_args_impl + 466
5   CoreFoundation                        0x7fff203e2a7e _CFLogvEx3 + 198
6   Foundation                            0x7fff207fd328 _NSLogv + 97
7   Foundation                            0x7fff207fd3c6 NSLog + 138
8   libSystem.Native.dylib                   0x10dff56db SystemNative_Log + 219
9   libmonosgen-2.0.dylib                    0x10fd6d282 do_icall + 146
10  libmonosgen-2.0.dylib                    0x10fd6bad7 do_icall_wrapper + 295
11  libmonosgen-2.0.dylib                    0x10fd5c7f6 mono_interp_exec_method + 3990
12  libmonosgen-2.0.dylib                    0x10fd59f63 interp_runtime_invoke + 259
13  libmonosgen-2.0.dylib                    0x10fe413bd mono_runtime_try_invoke + 157
14  libmonosgen-2.0.dylib                    0x10fe4478e mono_runtime_invoke + 478
15  libxamarin-dotnet-debug.dylib            0x10efdd42f xamarin_invoke_trampoline + 6303
16  libxamarin-dotnet-debug.dylib            0x10efe4d39 xamarin_arch_trampoline + 105
17  libxamarin-dotnet-debug.dylib            0x10efe5f1a xamarin_x86_64_common_trampoline + 118
18  UIKitCore                             0x7fff248dfeff -[UIViewController _setViewAppearState:isAnimating:] + 912
19  UIKitCore                             0x7fff248e0967 -[UIViewController __viewDidAppear:] + 146
20  UIKitCore                             0x7fff248e2545 __64-[UIViewController viewDidMoveToWindow:shouldAppearOrDisappear:]_block_invoke + 42
21  UIKitCore                             0x7fff248e12e2 -[UIViewController _executeAfterAppearanceBlock] + 75
22  UIKitCore                             0x7fff256001a9 -[_UIAfterCACommitBlock run] + 54
23  UIKitCore                             0x7fff256006a1 -[_UIAfterCACommitQueue flush] + 190
24  libdispatch.dylib                     0x7fff201148e4 _dispatch_call_block_and_release + 12
25  libdispatch.dylib                     0x7fff20115b25 _dispatch_client_callout + 8
26  libdispatch.dylib                     0x7fff20123043 _dispatch_main_queue_drain + 1050
27  libdispatch.dylib                     0x7fff20122c1b _dispatch_main_queue_callback_4CF + 31
28  CoreFoundation                        0x7fff20371ed5 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
29  CoreFoundation                        0x7fff2036c6ca __CFRunLoopRun + 2761
30  CoreFoundation                        0x7fff2036b704 CFRunLoopRunSpecific + 562
31  GraphicsServices                      0x7fff2cba9c8e GSEventRunModal + 139
32  UIKitCore                             0x7fff2509e65a -[UIApplication _run] + 928
33  UIKitCore                             0x7fff250a32b5 UIApplicationMain + 101
34  libxamarin-dotnet-debug.dylib            0x10efa04ca xamarin_UIApplicationMain + 58
35  libmonosgen-2.0.dylib                    0x10fd6d345 do_icall + 341
36  libmonosgen-2.0.dylib                    0x10fd6bad7 do_icall_wrapper + 295
37  libmonosgen-2.0.dylib                    0x10fd5c7f6 mono_interp_exec_method + 3990
38  libmonosgen-2.0.dylib                    0x10fd59f63 interp_runtime_invoke + 259
39  libmonosgen-2.0.dylib                    0x10fe402d8 mono_runtime_invoke_checked + 136
40  libmonosgen-2.0.dylib                    0x10fe47c1b mono_runtime_exec_main_checked + 107
41  libmonosgen-2.0.dylib                    0x10fcac742 mono_jit_exec + 354
42  libxamarin-dotnet-debug.dylib            0x10efe4bea xamarin_main + 1898
43  xxx.iOS                           0x10cc8acf4 main + 52 (main.x86_64.mm:77)
44  dyld_sim                                 0x10d802f21 start_sim + 10
45  dyld         

;;;;

Votes

0

Share

3 comments
Avatar
Anna Morozyuk
Created

Hello Nynke Van Der Heide ,

Thank you for reaching Rider Forum. 

From the crash dump provided, it might be only concluded that possibly the debugger could not connect after the application started. 

Could you please share more details: 

  1.  Do you run the application in debug mode? 
  2. Does the application start? 
  3. Do you have any Debug output? 
  4. Could you please collect logs with tracing in the way below: 
  •  Go to Help | Diagnostic tools | Choose Trace Scenarios;
  •  Enable the Trace scenario for Debugger (if it is a debug issue) and Multiplatorm (or Xamarin if your Rider. version is under 2024.1);
  •  Reproduce the issue;
  •  Collect the full log bundle via Help | Collect Logs and Diagnostic Data;
  •  Disable Trace scenarios;
  •  Attach the resulting log bundle to our server (https://uploads.jetbrains.com/) and share the ID.

Thank you in advance. Have a nice day. 

0
Avatar
Nynke Van Der Heide
Created

Hi Anna,

Thank you for your reply.

1. When I run the app in debug mode (app connected to Rider) the freeze doesn't occur. It also doesn't occur when I just click the run button and test the app with the simulator. When I run the app without a connection between Rider and the simulator, the freeze happens. I tried to reproduce the issue by doing the same thing via Visual Studio, but the freeze doesn't occur.

2. The applications starts but while using it, it freezes and I can't use the app anymore. I have to close the app by swiping up from the bottom of the screen, opening the multitasking view and swipe the app up.

3. I don't have the debug output because the freeze only happens when I build and install the app with Rider debug mode, quit the app and start the app again by tapping the app icon in the simulator.

4. 2024_07_26_iuddsXdt9pFMTkABWTLJHg

I just reproduced the issue again without doing anything special. It happened instantly.

Thank you.

0
Avatar
Anna Morozyuk
Created

Hello Nynke Van Der Heide ,

Thank you for the detailed explanation. 

At the moment, the behavior is still not very clear and cannot be reproduced. Could you please reproduce the issue with the new 2024.2.5 version and collect logs from Help > Collect Logs and Diagnostic Data with tracing this time on Multiplatform? Also, once you meet a freeze, could you please collect the dumps using the following instruction and attach all the resulting information to our server (https://uploads.jetbrains.com/) and share the ID? 

Thank you in advance!

0

Please sign in to leave a comment.