Native crash on Pixel device
See original GitHub issueHello,
I am seeing the following crash from the barcode scanner on the android-vision library at random times while scanning barcodes. It is most often present on the Pixel 2 running 8.1 but it has happened on other phones. Here is the version of the library i am using App’s google play service version: 11.8.0 Device’s google play service version: 12.5.29
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'google/walleye/walleye:8.1.0/OPM2.171019.029/4657601:user/release-keys'
Revision: 'MP1'
ABI: 'arm64'
pid: 22570, tid: 3821, name: Thread-63
nal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xc
Cause: null pointer dereference
x0 0000000000000000 x1 0000007e4603a580 x2 1fc0000000000000 x3 0000000000000003
x4 0000000000000000 x5 0000007e4b1ab208 x6 0000000000000001 x7 0000000200000001
x8 f629adbe4c927c77 x9 f629adbe4c927c77 x10 0000000000000009 x11 00000000ffffffff
x12 0000007e4dd946b0 x13 ffffffffffffffff x14 0000000000000000 x15 0000007e37a00000
x16 0000007ee57a5cb0 x17 0000007ee574252c x18 0000000000000000 x19 0000007d871fdae8
x20 0000007d871fdad0 x21 0000007d871fdc70 x22 0000000000000001 x23 0000000000000000
x24 0000000000000000 x25 0000000047760400 x26 0000000043da8000 x27 00000000443c0000
x28 0000000043820000 x29 0000007d871fe5a0 x30 0000007e45c66f3c
sp 0000007d871fda20 pc 0000007e45c66f44 pstate 0000000060000000
backtrace:
#00 pc 000000000001bf44 /data/data/com.google.android.gms/app_vision/barcode/libs/arm64-v8a/libbarhopper.so
#01 pc 000000000001110c /data/data/com.google.android.gms/app_vision/barcode/libs/arm64-v8a/libbarhopper.so
#02 pc 0000000000005bf4 /data/data/com.google.android.gms/app_vision/barcode/libs/arm64-v8a/libbarhopper.so
#03 pc 0000000000007674 /data/data/com.google.android.gms/app_vision/barcode/libs/arm64-v8a/libbarhopper.so
#04 pc 0000000000003624 /data/data/com.google.android.gms/app_vision/barcode/libs/arm64-v8a/libbarhopper.so
#05 pc 0000000000004c8c /data/data/com.google.android.gms/app_vision/barcode/libs/arm64-v8a/libbarhopper.so
#06 pc 0000000000553bf0 /system/lib64/libart.so (art_quick_generic_jni_trampoline+144)
#07 pc 000000000013f154 /dev/ashmem/dalvik-jit-code-cache (deleted)
Issue Analytics
- State:
- Created 5 years ago
- Comments:10
Top Results From Across the Web
Native crash on Android Google Play and TestLab #107264
Native crash on Android Google Play and TestLab #107264 ... I have same issue, works fine on dev machine with Pixel 2 emulator,...
Read more >Diagnosing Native Crashes | Android Open Source Project
The following sections include common types of native crash, an analysis of a sample crash dump, and a discussion of tombstones.
Read more >React Native App Crashes on Pixel Physical Device Without ...
I am currently facing a weired issue after upgrading to React Native 0.66.4 which causes my Android app to crash on Pixel Mobile...
Read more >Native Crash Google in 'com.google.android.gms:play ...
Hi! We have fixed the issue on Pixel devices, and have communicated to partners to take the fix for Android 11.
Read more >Fix an installed app that isn't working on a Pixel phone
Try the following steps if an app installed on your phone has any of these problems: Crashing. Won't open. Won't respond. Isn't working...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks for the report! This bug will be fixed in a future release.
Sorry, I can’t comment on the timing of future releases.
However, for reference, your crash doesn’t look related to the issue described in this thread (i.e. a null pointer dereference in the barcode reader’s native code).
I’m locking this thread until we have something to announce since we already understand the root cause.