IssueTracker

Hi Ed, Thank you so much for these suggestions. I've been reviewing them and merging them in. Hopefully it should be live. I've included a thank you note too in the article.

Also a crash on Sony  Xperia XA1 running Android 8.0.0

Fatal Exception: java.lang.IllegalStateException: maxImages (4) has already been acquired, call #close before acquiring more.
       at android.media.ImageReader.acquireNextImage(ImageReader.java:501)
       at android.media.ImageReader.acquireLatestImage(ImageReader.java:386)
       at androidx.camera.core.AndroidImageReaderProxy.c(AndroidImageReaderProxy.java:4)
       at androidx.camera.core.SafeCloseImageReaderProxy.acquireLatestImage(SafeCloseImageReaderProxy.java:5)
       at androidx.camera.core.ImageAnalysisNonBlockingAnalyzer.onImageAvailable(ImageAnalysisNonBlockingAnalyzer.java)
       at androidx.camera.core.SafeCloseImageReaderProxy.lambda$setOnImageAvailableListener$1(SafeCloseImageReaderProxy.java:2)
       at androidx.camera.core.-$$Lambda$SafeCloseImageReaderProxy$vlVuGMKvMVqmwbJFm3dTgGgUzu4.onImageAvailable(-.java:2)
       at androidx.camera.core.AndroidImageReaderProxy.lambda$setOnImageAvailableListener$0(AndroidImageReaderProxy.java:2)
       at androidx.camera.core.-$$Lambda$AndroidImageReaderProxy$ydxkGVJ03P0ZMYkq3dfSV-hzi3E.run(-.java:2)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
       at java.lang.Thread.run(Thread.java:764)

Thanks for the information.  It seems the issues still exists.
I think there must be a Image leakage  somewhere.   we will look into the issue with priority.  

Project: platform/frameworks/support
Branch: androidx-main

commit 9fd9b8d48bfef2c9abfcba4d4f0fba89a12f6875
Author: Xi Zhang <xizh@google.com>
Date:   Thu Jan 07 09:49:58 2021

    ImageAnalysis: acquire image when queue is maxed should not crash.
   
    Not sure what the exact cause of the bug b/175851631, but this CL is a step in the right direction. If the image queue is maxed out, acquiring a new image should not crash. This is a net improvment on user experience. It doesn't hide the issue either because if it happens preview is going to freeze.
   
    Changes:
    - refactor abstract analyzerto make the logic clear. Remove the open/close methods of the abstract analyzer, and replace it with the later introduced attach/detach concept. It should only forward images when 1) the user analzyer is set, and 2) the ImageAnalysis is attached to a camera.
    - Add a clearCache() method to release cached images. The method is called when 1) user analyzer is unset, 2) ImageAnalysis is detached, or 3) there is an error in creating pipeline.
    - In non-blocking analyzer, rely on posted image's existence to check if it's been closed.
    - try/catch the max queue exception and log it as an error.
    - clean up unit tests.
   
    Relnote: This change catches the exception when the image queue is maxed out in ImageAnalysis. So instead of crash, you may notice other use cases being frozen or sluggish. e.g. frozen/sluggish preview.
   
    Bug: 175851631
    Test: manual test and ./gradlew bOS
    Change-Id: Ic12dafa0b0feed875a07ea1d8c23c52977b15afa

M       camera/camera-camera2/src/androidTest/java/androidx/camera/camera2/ImageAnalysisTest.java
M       camera/camera-core/lint-baseline.xml
M       camera/camera-core/src/main/java/androidx/camera/core/ImageAnalysis.java
M       camera/camera-core/src/main/java/androidx/camera/core/ImageAnalysisAbstractAnalyzer.java
M       camera/camera-core/src/main/java/androidx/camera/core/ImageAnalysisBlockingAnalyzer.java
M       camera/camera-core/src/main/java/androidx/camera/core/ImageAnalysisNonBlockingAnalyzer.java
M       camera/camera-core/src/test/java/androidx/camera/core/ImageAnalysisNonBlockingAnalyzerTest.java

https://android-review.googlesource.com/1545504

Hi Ventatesh,

I tried to reproduce it using your approach (by stress testing CaptureFragment<->GalleryFragment on CameraXBasic app) on several devices.  
But still failed to reproduce it.  

Could you kindly clarify the below questions?
(1) Confirm if there is anything modified in your CameraXBasic app
(2) Clarify what the chance is to reproduce it ? For example,  reproduce once after keep switching for 5 minutes.  
(3) Does it happen on all devices or only on specific devices ?  Please give us the device name if it happens on specific devices.

Hi Venkatesh,

Please see Scott's comment#9 - we're trying to track this down for our next release - we're closing our next build soon - please let us know if you can comment on the questions - thanks!

Could you kindly clarify the below questions?
(1) Confirm if there is anything modified in your CameraXBasic app
No. We have attached all 3 use cases.

(2) Clarify what the chance is to reproduce it ? For example,  reproduce once after keep switching for 5 minutes.  
1 in 50. It has 0.1-0.2% instance in our production environment.

(3) Does it happen on all devices or only on specific devices ?  Please give us the device name if it happens on specific devices.
It happen on specific devices. Attached is the list of devices on which we see this issue in producton.

Hi Vishal,
Thanks ! This is quite useful.  We are trying to get one of the devices and reproducing on other devices as well.  Will let you know if there is any result.

Scott,
Our app is on play store. Just search for Microsoft Lens on play store.


On Fri, Mar 19, 2021, 12:49 PM <buganizer-system@google.com> wrote:

The crash is intermittent. We have observed sometimes it happened after 10
mins of using the app, sometimes it happened on app open itself when camera
is opened for first time.
So there is no set pattern.

In current production it is beta05.
We will have alpha02 around April in prod.

On Mon, Mar 22, 2021, 9:35 AM <buganizer-system@google.com> wrote: