Status Update
No update yet.
Comments
wu...@google.com
ch...@google.com
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
pr...@paralleldots.com
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
wu...@google.com
ch...@google.com
ap...@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.
ch...@google.com
pr...@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.
Description
CAMERAX VERSION 1.3.4
CAMERA APPLICATION NAME AND VERSION: Shelfwatch and 5.3.0
DEVICE NAME:
Samsung Galaxy S10e
Samsung Galaxy A24
Samsung Galaxy S10+
Samsung Galaxy S20 +/FE
DESCRIPTION: Users are facing crashes while taking images, does not happen for all images but happens randomly.
STEPS TO REPRODUCE:
1. Click multiple images with camera x library
REPRODUCIBILITY: As this is faced by our users on specific devices we have not reproduced but from the logs it seems like it happens for 1/20 pictures.
STACK TRACE :
Fatal Exception: java.lang.UnsupportedOperationException: Decode jpeg byte array failed
at androidx.camera.core.internal.utils.ImageUtil.createBitmapFromJpegImage(ImageUtil.java:453)
at androidx.camera.core.internal.utils.ImageUtil.createBitmapFromImageProxy(ImageUtil.java:82)
at androidx.camera.core.ImageProxy.toBitmap(ImageProxy.java:154)
Additonal comments :
Have upgraded to 1.3.4 version of Camera X for the fix in Galaxy A24, will it be fixed for other devices as well?