Jump to content

Our App exited abnormally


JennyKIM

Recommended Posts

  • 1 month later...

Hello, @JennyKIM,

It seems that the crash originates from Unity native libraries.

 

09-01 18:50:47.154 24050 24085 E CRASH   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

09-01 18:50:47.154 24050 24085 E CRASH   : Version '2019.4.18f1c1 (6ddd89a99571)', Build type 'Release', Scripting Backend 'mono', CPU 'armeabi-v7a'

09-01 18:50:47.154 24050 24085 E CRASH   : Build fingerprint: 'HTC/kona/kona:10/QKQ1.210319.001/2557:user/release-keys'

09-01 18:50:47.154 24050 24085 E CRASH   : Revision: '0'

09-01 18:50:47.154 24050 24085 E CRASH   : ABI: 'arm'

09-01 18:50:47.154 24050 24085 E CRASH   : Timestamp: 2021-09-01 18:50:47+0800

09-01 18:50:47.154 24050 24085 E CRASH   : pid: 24050, tid: 24085, name: UnityMain  >>> com.dengxianxr.cosmos <<<

09-01 18:50:47.154 24050 24085 E CRASH   : uid: 10213

09-01 18:50:47.154 24050 24085 E CRASH   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0

09-01 18:50:47.154 24050 24085 E CRASH   : Cause: null pointer dereference

09-01 18:50:47.154 24050 24085 E CRASH   :     r0  bd7b3c00  r1  003fffe9  r2  00000001  r3  003fffdc

09-01 18:50:47.154 24050 24085 E CRASH   :     r4  00000000  r5  00000000  r6  00000010  r7  00003a00

09-01 18:50:47.154 24050 24085 E CRASH   :     r8  00003947  r9  e5624260  r10 00003957  r11 00001d10

09-01 18:50:47.154 24050 24085 E CRASH   :     ip  000000ff  sp  ba7e8cd0  lr  badabcb9  pc  bb46f45a

09-01 18:50:47.154 24050 24085 E CRASH   :

09-01 18:50:47.154 24050 24085 E CRASH   : backtrace:

09-01 18:50:47.154 24050 24085 E CRASH   :       #00 pc 0096445a  /data/app/com.dengxianxr.cosmos-d7VdFRBttU6lXG1U342T5w==/lib/arm/libunity.so

09-01 18:50:47.154 24050 24085 E CRASH   :       #01 pc 002a0cb5  /data/app/com.dengxianxr.cosmos-d7VdFRBttU6lXG1U342T5w==/lib/arm/libunity.so

09-01 18:50:47.154 24050 24085 E CRASH   :       #02 pc 0029d4e5  /data/app/com.dengxianxr.cosmos-d7VdFRBttU6lXG1U342T5w==/lib/arm/libunity.so

 

Another finding is that, right before the crash stack, there is this line:

09-01 18:50:46.834 24050 24080 W VRWatchDog: SUBMIT-TIMEOUT WARNING: 1161 ms

 

Which might suggest the application was frozen before it crashed.

However, as suggested at the beginning, the crash stack originates from Unity native libraries which means that it is pretty much impossible for us to find the root cause of this crash.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...