Intermittent Crash that we can not get a root cause.

Question

Created Mar ’22

Replies 3

Boosts 0

Views 2.4k

Participants 2

This is a Unity APP that uses the Apple Lidar camera to record 3D Human movement. Was looking for an extra set of eyes to review the logs.

When running the App we have about 300 MB of free memory on the IPAD Pro 8 GB. The Crash logs are consistent. Is this a memory resource issue? Could we extend the memory to beyond 5 GB to help with this issue?

Kernel Triage: VM - pmap_enter failed with resource shortage VM - pmap_enter failed with resource shortage VM - pmap_enter failed with resource shortage VM - pmap_enter failed with resource shortage VM - pmap_enter failed with resource shortage

Thread 0 crashed with ARM Thread State (64-bit): x0: 0x0000000000000104 x1: 0x0000000000000000 x2: 0x0000000000008400 x3: 0x0000000000000000 x4: 0x0000000000000000 x5: 0x00000000000000a0 x6: 0x0000000000000000 x7: 0x0000000000000000 x8: 0x000000016f064098 x9: 0x0000000000008401 x10: 0x0000000130421820 x11: 0x0000000000000002 x12: 0x0000000000000000 x13: 0x0000000000000000 x14: 0x0000000000000000 x15: 0x0000000000000001 x16: 0x0000000000000131 x17: 0x0000000000000000 x18: 0x000000013dd2486c x19: 0x0000000130421808 x20: 0x0000000130421848 x21: 0x00000001010b4660 x22: 0x0000000000000000 x23: 0x0000000000000000 x24: 0x0000000000008400 x25: 0x0000000000008401 x26: 0x0000000000008500 x27: 0x00000000000003e8 x28: 0x00000000000f4240 fp: 0x000000016f064110 lr: 0x00000001f2e3a254 sp: 0x000000016f064080 pc: 0x00000001b973df90 cpsr: 0x60001000 esr: 0x56000080 Address size fault

crashlog.crash

Boost

Answer 1

DTS Engineer OP

Apple

Mar ’22

The Kernel Triage section is probably a red herring. What matters is this:

Termination Reason: FRONTBOARD 2343432205 
<RBSTerminateContext| domain:10 code:0x8BADF00D …

The 0x8BADF00D (ate bad food) code means that your app was killed by the system for being unresponsive. For more background on this, see Addressing Watchdog Terminations.

Looking at your main thread backtrace, I see this:

Thread 0 name:
Thread 0 Crashed:
0   libsystem_kernel.dylib  … __psynch_cvwait + 8
1   libsystem_pthread.dylib … _pthread_cond_wait + 1228 (pthread_cond.c:636)
2   UnityFramework          … il2cpp::os::posix::PosixWaitObject::Wait(unsigned int, bool) + 404 (PosixWaitObject.cpp:119)

Something deep (deep deep) in your third-party runtime is stuck waiting on a pthread condition variable. I’ve no idea why that might be; it’s someting you’d have to escalate with your that runtime’s vendor.

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

0

Answer 2

Daveinthehat OP

Mar ’22

Hi Quinn, we are still struggling. I have two new crash files. Would be able to have a look at them to see if you see any new patterns?

crashlog.crash

.

crashlog.crash

0

Answer 3

DTS Engineer OP

Apple

Mar ’22

On the face of it those two crashes are very different. Your app is taking a memory access exception:

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

Again, the backtrace is all code from your third-party runtime:

Thread 53 name:
Thread 53 Crashed:
0   libsystem_platform.dylib … _platform_memmove + 52
1   UnityFramework           … Sensor_Stream_mFF850E96E26ADC438DFA62EFFABFDAEDE3B6DEEC + 632 (LightBuzz.BodyTracking.cpp:24277)
2   UnityFramework           … Action_Invoke_m3FFA5BE3D64F0FF8E1E1CB6F953913FADB5EB89E + 276
3   UnityFramework           … VirtActionInvoker0::Invoke(unsigned short, Il2CppObject*) + 20 …
4   UnityFramework           … Task_Execute_m35673A0487248C5577449A4A3FBDF7FD3B6BA086 + 140 …
5   UnityFramework           … ContextCallback_Invoke_mF4F8496213E8F0925947DD8994A477AE2E54EFDF + 408
6   UnityFramework           … ExecutionContext_RunInternal_mC5D58D6EDE270B4CDA05181E9064E040D6692B2B + 376 …
7   UnityFramework           … Task_ExecuteWithThreadLocal_m25476BDF5AAFF102A95E92CB1E0989DFF72408A8 + 404 …
8   UnityFramework           … Task_ExecuteEntry_m55634616576BB085EF3CEDB04801C4183FE1B053 + 300 …
9   UnityFramework           … InterfaceActionInvoker0::Invoke(unsigned short, Il2CppClass*, Il2CppObject*) + 84 …
10  UnityFramework           … ThreadPoolWorkQueue_Dispatch_mCC5743D99870EC7844CAB3FF3FA7D23A44A4A984 + 736 …
11  UnityFramework           … RuntimeInvoker_FalseSByte_t928712DD662DC29BA4FAAE8CE2230AFB23447F0B…
12  UnityFramework           … worker_thread(void*) + 324 …
13  UnityFramework           … il2cpp::vm::ThreadStart(void*) + 80 …
14  UnityFramework           … il2cpp::os::Thread::RunWrapper(void*) + 88 …
15  UnityFramework           … il2cpp::os::ThreadImpl::ThreadStartWrapper(void*) + 40 …
16  libsystem_pthread.dylib  … _pthread_start + 148 (pthread.c:891)
17  libsystem_pthread.dylib  … thread_start + 8

The only thing that stands out here is the source file and line in frame 1, namely LightBuzz.BodyTracking.cpp:24277.

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

0