ImageCapture halt the preview [193864120]

Fixed

Bug

Status Update

No update yet.

Description

le...@google.com

created issue #1

Jul 16, 2021 08:28AM

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-alpha07)
androidx.camera:camera-core:1.1.0-alpha05

CAMERA APPLICATION NAME AND VERSION: (Settings > Apps > (app name) > version)

ANDROID OS BUILD NUMBER: (Settings > About > Build number)

DEVICE NAME: (Nexus 5X, Samsung S6, etc)

DESCRIPTION:

LIST ANY EXPERIMENTAL FEATURES: (As an example - @ExperimentalCamera2Interop)

STEPS TO REPRODUCE:

Bind Preview + ImageCapture + VideoCapture
Invoke ImageCapture.takePicture()

OBSERVED RESULTS:
Preview halt for a while until image is captured.

EXPECTED RESULTS:
Smooth Preview

REPRODUCIBILITY: (5 of 5, 1 of 100, etc)
5/5

ADDITIONAL INFORMATION:

CODE FRAGMENTS (this will help us troubleshoot your issues):

Comments

ap...@google.com <ap...@google.com> #2Jul 23, 2021 05:41PM

A couple of questions:

1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?

ap...@google.com <ap...@google.com> #3Jul 23, 2021 05:41PM

Tested on Android 12 Emulator with custom executor, but cannot repro this issue.

le...@google.com <le...@google.com> Jul 23, 2021 05:43PM

Marked as fixed.

ra...@gmail.com <ra...@gmail.com> #4Aug 2, 2021 03:06AM

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.

le...@google.com <le...@google.com> #5Aug 2, 2021 03:59AM

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.

Issue 193864120