crash at androidx.camera.core.internal.YuvToJpegProcessor$ByteBufferOutputStream.write()(YuvToJpegProcessor.java:255) [192017012]

Fixed

Bug

Status Update

No update yet.

Description

li...@gmail.com

created issue #1

Jun 25, 2021 11:04AM

CAMERAX VERSION (1.0.0)

ANDROID OS BUILD NUMBER: Android 11

DEVICE NAME: Samsung Galaxy S21, Samsung Galaxy Note20 5G, Samsung Galaxy Note10+

DESCRIPTION:

CRASH TYPE SUMMARY
LOCATION
YuvToJpegProcessor.java line 255 in androidx.camera.core.internal.YuvToJpegProcessor$ByteBufferOutputStream.write()
EXCEPTION
java.io.EOFException
MESSAGE
Output ByteBuffer has insufficient bytes remaining.

log:

java.io.EOFException: Output ByteBuffer has insufficient bytes remaining.
	at androidx.camera.core.internal.YuvToJpegProcessor$ByteBufferOutputStream.write()(YuvToJpegProcessor.java:255)
	at java.io.BufferedOutputStream.flushBuffer()(BufferedOutputStream.java:82)
	at java.io.BufferedOutputStream.flush()(BufferedOutputStream.java:140)
	at java.io.FilterOutputStream.flush()(FilterOutputStream.java:146)
	at android.graphics.YuvImage.nativeCompressToJpeg()(YuvImage.java:-2)
	at android.graphics.YuvImage.compressToJpeg()(YuvImage.java:141)
	at androidx.camera.core.internal.YuvToJpegProcessor.process()(YuvToJpegProcessor.java:141)
	at androidx.camera.core.CaptureProcessorPipeline.postProcess()(CaptureProcessorPipeline.java:144)
	at androidx.camera.core.CaptureProcessorPipeline$1.onImageAvailable()(CaptureProcessorPipeline.java:124)
	at androidx.camera.core.AndroidImageReaderProxy.lambda$setOnImageAvailableListener$0()(AndroidImageReaderProxy.java:139)
	at androidx.camera.core.AndroidImageReaderProxy.lambda$setOnImageAvailableListener$0$AndroidImageReaderProxy()(AndroidImageReaderProxy.java:0)
	at androidx.camera.core.-$$Lambda$AndroidImageReaderProxy$ydxkGVJ03P0ZMYkq3dfSV-hzi3E.run()(-.java:4)
	at java.util.concurrent.ThreadPoolExecutor.runWorker()(ThreadPoolExecutor.java:1167)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run()(ThreadPoolExecutor.java:641)
	at java.lang.Thread.run()(Thread.java:923)

ADDITIONAL INFORMATION:

Looks like it only happens on Samsung device with android 11

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

Comments

tr...@google.com <tr...@google.com> #2Jun 28, 2021 06:21PM

It could easy to reproduce when turning on "Don't keep activities".

[Deleted User] <[Deleted User]> #3Jun 28, 2021 06:38PM

Comment has been deleted.

Message last modified on Jun 28, 2021 06:38PM

li...@gmail.com <li...@gmail.com> #4Jun 28, 2021 06:39PM

Thanks Ian! Looking forward to a new alpha release ASAP rather than monthly release.😅

ch...@google.com <ch...@google.com> #5Jun 29, 2021 01:25AM

Reassigned to ch...@google.com.

Thanks for fixing this!

li...@gmail.com <li...@gmail.com> #6Jun 29, 2021 12:30PM

Wondering is there any release plan?

ch...@google.com <ch...@google.com> #7Jun 30, 2021 10:10AM

Fragments 1.1.0-alpha02 is out now with this fix.

tr...@google.com <tr...@google.com> #8Jun 30, 2021 06:20PM

Does Preferences also depend on Fragments? In which case when will that be updated to 1.1.0-alpha02? Or is the recommended practice to specify both Preferences and Fragments in build.gradle so that we can force Fragments 1.1.0-alpha02?

ch...@google.com <ch...@google.com> #9Jul 1, 2021 10:13AM

Re #8 - yes, if you need a specific version of Fragments, you should specify both Preferences and Fragments in your build.gradle.

The release schedule of AndroidX components is completely independent of one another, so Preferences will only get a new version when there's something new to release in Preferences.

li...@gmail.com <li...@gmail.com> #10Jul 1, 2021 10:45AM

So, in general it sounds like if an androidx dependency (such as preference) is added to build.gradle, then any dependencies of that (e.g. fragment) should also be explicitly added so that the specific version can be specified. Is that right?

In other words, when we explicitly include preference-1.1.0-alpha01 we need to be aware that the fragment-alpha1.1.0-alpha01 is automatically being brought in and so might affect the fragment behaviour. Sorry, I know this is rather OT.

tr...@google.com <tr...@google.com> #11Jul 1, 2021 10:19PM

Thanks, fix confirmed

ch...@google.com <ch...@google.com> #12Jul 2, 2021 09:58AM

alpha02 version of fragments didn't fix this for me. Is there another solution?

ap...@google.com <ap...@google.com> #13Jul 13, 2021 04:21AM

Re #12 - you're most likely hitting

https://issuetracker.google.com/issues/120814739 - a related but separate issue fixed for alpha03

ch...@google.com <ch...@google.com> #14Jul 13, 2021 05:40AM

Marked as fixed.

Run