Native ocr lib crash
See original GitHub issueOur app uses text and barcode detection, and a very small minority have been experiencing this crash. I can only see the crash through Google Play and not through our Crashlytics integration. The devices have only been various new-ish Samsung devices running Nougat (both 7 and 7.1), but majority with those same specs have been fine. The crash happens consistently with those users though, and effectively renders our in-app camera non-functional for them.
Is there anything I could do in-app to prevent this or is this a library bug? We do check if the detectors are operational before using them.
native: pc 000000000006fc2c /system/lib64/libc.so (tgkill+8)
native: pc 000000000006cf40 /system/lib64/libc.so (pthread_kill+64)
native: pc 00000000000251f8 /system/lib64/libc.so (raise+24)
native: pc 000000000001ccc4 /system/lib64/libc.so (abort+52)
native: pc 00000000004750d0 /data/data/com.google.android.gms/app_vision/ocr/libs/arm64-v8a/libocr.so
native: pc 0000000000475770 /data/data/com.google.android.gms/app_vision/ocr/libs/arm64-v8a/libocr.so
native: pc 0000000000475814 /data/data/com.google.android.gms/app_vision/ocr/libs/arm64-v8a/libocr.so
native: pc 0000000000474830 /data/data/com.google.android.gms/app_vision/ocr/libs/arm64-v8a/libocr.so
native: pc 000000000026cee4 /data/data/com.google.android.gms/app_vision/ocr/libs/arm64-v8a/libocr.so
native: pc 0000000000271190 /data/data/com.google.android.gms/app_vision/ocr/libs/arm64-v8a/libocr.so
native: pc 0000000000065794 /data/data/com.google.android.gms/app_vision/ocr/libs/arm64-v8a/libocr.so
native: pc 0000000000065488 /data/data/com.google.android.gms/app_vision/ocr/libs/arm64-v8a/libocr.so
native: pc 000000000027caf4 /data/data/com.google.android.gms/app_vision/ocr/libs/arm64-v8a/libocr.so
native: pc 0000000000280274 /data/data/com.google.android.gms/app_vision/ocr/libs/arm64-v8a/libocr.so
native: pc 0000000000067c84 /data/data/com.google.android.gms/app_vision/ocr/libs/arm64-v8a/libocr.so
native: pc 0000000000067f64 /data/data/com.google.android.gms/app_vision/ocr/libs/arm64-v8a/libocr.so
native: pc 0000000000063dec /data/data/com.google.android.gms/app_vision/ocr/libs/arm64-v8a/libocr.so
native: pc 000000000038c5e0 /data/user_de/0/com.google.android.gms/app_chimera/m/0000002b/oat/arm64/DynamiteModulesA_GmsCore_prodmnc_xxhdpi_release.odex
Issue Analytics
- State:
- Created 6 years ago
- Reactions:7
- Comments:98 (12 by maintainers)
Top Results From Across the Web
How can i handle native crash in my app due to Google Ocr lib ...
I have implemented some logic in App side to reduce crashes. From App side we can do one thing which will minimize crashes....
Read more >Developers - Native ocr lib crash - - Bountysource
Our app uses text and barcode detection, and a very small minority have been experiencing this crash. I can only see the crash...
Read more >Android Question [SOLVED] OCR Mobilevision crash - B4X
Hello, Here is the log from my app. I trying to get an OCR library to work. I'm trying mobilevision by Donmanfred but...
Read more >Bug Reporting - PSPDFKit
If PSPDFKit is crashing natively (i.e. inside the native libraries), please provide us with a native crash dump. You can define the path...
Read more >Changelog | Genius Scan SDK
[Android ScanFlow] Use CameraX instead of the legacy Camera API on most ... [OCR] Return a proper exception in java instead of crashing...
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
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
we are losing so many users oh god could you please hurry up this is really destroying our app
It’s currently in beta channel and will roll out in the following weeks, you cannot force your App use the beta Google Play Services. At the meantime I’d suggest disable the OCR feature on devices that may crash.
Again we apologize for the crash. We do have unit tests, but unfortunately we didn’t run these tests on all devices.