Native crash in libarcore_c.so

Noltibus commented 4 years ago

SPECIFIC ISSUE ENCOUNTERED

The following stack trace pops up often in our crash reports: (This is the one from all phones EXCEPT the Pixel)

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
pid: 0, tid: 0 >>> one.realnote.app <<<

backtrace:
  #00  pc 0000000000083360  /apex/com.android.runtime/lib64/bionic/libc.so (abort+176)
  #00  pc 0000000001bd6f94  /data/app/com.google.ar.core-l-kc2GpoPkJGTv-eXfr3Hg==/base.apk!libarcore_c.so (offset 0x7c5000)
  #00  pc 0000000001bd6f60  /data/app/com.google.ar.core-l-kc2GpoPkJGTv-eXfr3Hg==/base.apk!libarcore_c.so (offset 0x7c5000)
  #00  pc 0000000001bd6be4  /data/app/com.google.ar.core-l-kc2GpoPkJGTv-eXfr3Hg==/base.apk!libarcore_c.so (offset 0x7c5000)
  #00  pc 0000000001bd6588  /data/app/com.google.ar.core-l-kc2GpoPkJGTv-eXfr3Hg==/base.apk!libarcore_c.so (offset 0x7c5000)
  #00  pc 0000000001bd7378  /data/app/com.google.ar.core-l-kc2GpoPkJGTv-eXfr3Hg==/base.apk!libarcore_c.so (offset 0x7c5000)
  #00  pc 0000000000c2cbb4  /data/app/com.google.ar.core-l-kc2GpoPkJGTv-eXfr3Hg==/base.apk!libarcore_c.so (offset 0x7c5000)
  #00  pc 0000000000c2d8cc  /data/app/com.google.ar.core-l-kc2GpoPkJGTv-eXfr3Hg==/base.apk!libarcore_c.so (offset 0x7c5000)
  #00  pc 0000000000c31c34  /data/app/com.google.ar.core-l-kc2GpoPkJGTv-eXfr3Hg==/base.apk!libarcore_c.so (offset 0x7c5000)
  #00  pc 0000000001a6d5f0  /data/app/com.google.ar.core-l-kc2GpoPkJGTv-eXfr3Hg==/base.apk!libarcore_c.so (offset 0x7c5000)
  #00  pc 00000000000e3b24  /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+36)
  #00  pc 0000000000085330  /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64)

And this stacktrace kind of looks similar but has a few differences and comes from the Google Pixel 2:

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
pid: 0, tid: 0 >>> one.realnote.app <<<

backtrace:
  #00  pc 00000000000821a0  /apex/com.android.runtime/lib64/bionic/libc.so (abort+176)
  #00  pc 0000000001e8b558  /data/app/com.google.ar.core-rjmKC5f13AmyfwNx33y6pw==/split_config.arm64_v8a.apk!libarcore_c.so (offset 0x1000)
  #00  pc 0000000001e8b524  /data/app/com.google.ar.core-rjmKC5f13AmyfwNx33y6pw==/split_config.arm64_v8a.apk!libarcore_c.so (offset 0x1000)
  #00  pc 0000000001e8b1e8  /data/app/com.google.ar.core-rjmKC5f13AmyfwNx33y6pw==/split_config.arm64_v8a.apk!libarcore_c.so (offset 0x1000)
  #00  pc 0000000001e8ab8c  /data/app/com.google.ar.core-rjmKC5f13AmyfwNx33y6pw==/split_config.arm64_v8a.apk!libarcore_c.so (offset 0x1000)
  #00  pc 0000000001e8b93c  /data/app/com.google.ar.core-rjmKC5f13AmyfwNx33y6pw==/split_config.arm64_v8a.apk!libarcore_c.so (offset 0x1000)
  #00  pc 0000000000d432ec  /data/app/com.google.ar.core-rjmKC5f13AmyfwNx33y6pw==/split_config.arm64_v8a.apk!libarcore_c.so (offset 0x1000)
  #00  pc 0000000000d4403c  /data/app/com.google.ar.core-rjmKC5f13AmyfwNx33y6pw==/split_config.arm64_v8a.apk!libarcore_c.so (offset 0x1000)
  #00  pc 0000000000d4847c  /data/app/com.google.ar.core-rjmKC5f13AmyfwNx33y6pw==/split_config.arm64_v8a.apk!libarcore_c.so (offset 0x1000)
  #00  pc 0000000001c59da4  /data/app/com.google.ar.core-rjmKC5f13AmyfwNx33y6pw==/split_config.arm64_v8a.apk!libarcore_c.so (offset 0x1000)
  #00  pc 00000000000e230c  /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+36)
  #00  pc 0000000000083d98  /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64)

VERSIONS USED

Android Studio: 4.0.1
ARCore SDK for Android: 1.18
Device manufacturer, model, and O/S: Motorola One Vision, Samsung Galaxy S9+, Samsung Galaxy S9, Xiaomi POCO F1, OnePlus OnePlus5T (all with Android 10), EDIT: Also Google Pixel 2 with Android 10
ARCore: 1.18 On Windows, use: adb shell pm dump com.google.ar.core | findstr /i "packages: versionName" On macOS, use: adb shell pm dump com.google.ar.core | egrep -i versionName\|packages:
Output of adb shell getprop ro.build.fingerprint:

STEPS TO REPRODUCE THE ISSUE

This crash pops up quite often in our Google Play crash reports. we have no idea how to exactly reproduce it.

WORKAROUNDS (IF ANY)

None

ADDITIONAL COMMENTS

devbridie commented 4 years ago

Thank you for reporting-- looking into it now.

plottsjp commented 2 years ago

@devbridie did you ever find anything out about this bug? Thank you

google-ar / arcore-android-sdk