Status Update
No update yet.
Comments
an...@photomath.com
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
an...@photomath.com
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
ma...@google.com
-
Second crash in the description is from a real device. Experienced it myself on two different Xiaomi phones, plus lots of crashes from users in the Google Play console.
-
Dynamic features are not used in the application.
As a wild guess, I have downgraded build tools from 31.0.0 to 30.0.3, compileSdk from 31 to 30, and moved all work with Language ID to the service in a separate process (just to be sure that crash can kill secondary process instead of main). This combination is in beta for 2 days by now and I don't see any SIGSEGV crashes.
er...@google.com
Hmm, I feel the crash might be something related to separate/secondary process.
I also changed compileSdk and targetSDK to 31 but still cannot repro this issue.
ap...@google.com
On the contrary, there was no separate process before, when crashes started.
In the new build (with the aforementioned changes) I can see SIGSEGV crash, but only one instead of dozens and it has a bit different backtrace:
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)
liblanguage_id_jni.so (offset 0x11e000)
backtrace:
#00 pc 000000000003c7c0 /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
#00 pc 000000000003b960 /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
#00 pc 000000000003bb48 /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
#00 pc 000000000003bafc /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
#00 pc 0000000000036c98 /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
#00 pc 0000000000032714 /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
#00 pc 0000000000031cac /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
#00 pc 0000000000057438 /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/oat/arm64/base.odex (offset 0x57000)
ni...@google.com
sh...@gmail.com
FYI, ML Kit launched a new language ID SDK in the latest release, which uses a new language ID model.
Could you try the new SDK version(17.0.0) to check if you can still repro this native crash? Thanks!
Description
Please note: This component is for the CameraX API used in Jetpack. Please DO NOT file Pixel Camera issues here.
Please describe your issue and include details such as the version of CameraX you are using and any relevant logs related to your issue.
If at all possible, capture an Android logcat (https://developer.android.com/studio/command-line/logcat ) when you're experiencing the issue, preferably while
the camera is still active.
CAMERAX VERSION (ex - 1.0.0-beta01)
CAMERA APPLICATION NAME AND VERSION: (Settings > Apps > (app name) > version) all os version
ANDROID OS BUILD NUMBER: (Settings > About > Build number) all builds
DEVICE NAME: (Nexus 5X, Samsung S6, etc) All devices, but visible in Nexus 5, Nexus 6P
DESCRIPTION: The ImageProxy returned by ImageCapture.OnImageCapturedCallback.onCaptureSuccess() has the incorrect rotation. The rotation value is mismatched with the exif of the JPEG buffer.
STEPS TO REPRODUCE:
OBSERVED RESULTS: The ImageProxy returned by ImageCapture.OnImageCapturedCallback.onCaptureSuccess() has the incorrect rotation. The rotation value is mismatched with the exif of the JPEG buffer.
EXPECTED RESULTS: The ImageProxy returned by ImageCapture.OnImageCapturedCallback.onCaptureSuccess() has the same rotation value as the rotation in the JPEG buffer exif.
REPRODUCIBILITY: (5 of out 5, 1 out of 100, etc) 5 out of 5 ADDITIONAL INFORMATION:
CODE FRAGMENTS (this will help us troubleshoot your issues):