Crash : IllegalArgumentException Can not get supported output size under supported maximum for the format: 34 [150506192]

Fixed

Bug

Status Update

No update yet.

Description

vi...@gmail.com

created issue #1

Feb 29, 2020 03:18AM

CAMERAX VERSION (ex - 1.0.0-alpha07)

1.0.0-alpha07

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

name : FUJITSU arrowsM04
Android OS version : 7.1.1

name: FUJITSU F-04J
Android OS version : 6.0.1

name: FUJITSU F-05J
Android OS version : 7.1.1

DESCRIPTION:

We receive following crash report from our app user.

Fatal Exception: java.lang.IllegalArgumentException: Can not get supported output size under supported maximum for the format: 34
at a.c.a.b.k0.a + 98(SupportedSurfaceCombination.java:98)
at a.c.a.b.k0.a + 30(SupportedSurfaceCombination.java:30)
at a.c.a.b.t.a + 22(Camera2DeviceSurfaceManager.java:22)
at androidx.camera.core.k1.a + 98(CameraX.java:98)
at androidx.camera.core.k1.a + 22(CameraX.java:22)
at a.c.b.c.a + 6(ProcessCameraProvider.java:6)
at <out app package name>.CameraFragment.a + 33(CameraFragment.kt:33)
at <out app package name>.CameraFragment.a + 1(CameraFragment.kt:1)
at <out app package name>.CameraFragment$m.run + 1(CameraFragment.kt:1)
at android.os.Handler.handleCallback + 751(Handler.java:751)
at android.os.Handler.dispatchMessage + 95(Handler.java:95)
at android.os.Looper.loop + 154(Looper.java:154)
at android.app.ActivityThread.main + 6262(ActivityThread.java:6262)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run + 890(ZygoteInit.java:890)
at com.android.internal.os.ZygoteInit.main + 780(ZygoteInit.java:780)

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

We receive this crash report from only three devices. And these devices's manufacturer is FUJITSU.

ADDITIONAL INFORMATION:

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

Our app bind usecases by following code.

private fun bindCameraUseCases(processCameraProvider: ProcessCameraProvider) {
preview = Preview.Builder().apply {
setTargetAspectRatio(AspectRatio.RATIO_4_3)
}.build().apply {
previewSurfaceProvider = binding.previewViewCamera.previewSurfaceProvider
}

imageCapture = ImageCapture.Builder().apply {
setCaptureMode(ImageCapture.CaptureMode.MINIMIZE_LATENCY)
setTargetAspectRatio(AspectRatio.RATIO_4_3)
setFlashMode(FlashMode.OFF)
}.build()

val cameraSelector = CameraSelector.Builder().requireLensFacing(LensFacing.BACK).build()
processCameraProvider.bindToLifecycle(viewLifecycleOwner, cameraSelector, preview, imageCapture)
}

Comments

er...@google.com <er...@google.com> #2Mar 2, 2020 11:39PM

Reassigned to vi...@gmail.com.

what is in update.zip ? can you share that file to triage this issue

er...@google.com <er...@google.com> #3Mar 4, 2020 06:16PM

Reassigned to ca...@google.com.

MHC19Q for Nexus 5X (bullhead) -

https://dl.google.com/dl/android/aosp//bullhead-ota-mhc19q-8fe67a2b.zip
N4F26T for Nexus 5X (bullhead) -

https://dl.google.com/dl/android/aosp/bullhead-ota-n4f26t-648ce802.zip
WW-12.2.5.23 for Asus ZenFone Go (ASUS_X014D) -

http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZB452KG/UL-ASUS_X014D-WW-12.2.5.23-user.zip

Look like, this happens only with a big images.

ch...@google.com <ch...@google.com> Mar 5, 2020 02:41AM

Reassigned to ch...@google.com.

ch...@google.com <ch...@google.com> #4Mar 5, 2020 02:59AM

On Windows 10 (x64)

ch...@google.com <ch...@google.com> Mar 9, 2020 11:09AM

Accepted by ch...@google.com.

vi...@gmail.com <vi...@gmail.com> #5Mar 11, 2020 07:15AM

related to (and probably worked around for now by) internal bug

http://b/36046324

i do think we should also start shipping a 64-bit Windows platform tools package.

we should also consider changing android::base::ReadFdToString to call fstat and pre-size the vector. not worthwhile for reading things like /proc/uptime, but the default expansion behavior for a huge file like a full OTA update is going to result in substantial overhead. (which will explain the regression between .3 and .4, since the former will have allocated exactly the necessary number of bytes.)

lastly (and maybe not worth doing at all, depending on how soon we can get folks to use a 64-bit platform tools on Windows, since all the other platforms are already 64-bit-only), we could consider rewriting the adb sideload code to (a) mmap/munmap rather than actually read in to physical memory or (b) pread. i'm not sure what the performance impact of pread would be (especially on Windows where there is no pread equivalent).

ch...@google.com <ch...@google.com> #6Mar 18, 2020 07:49AM

Marked as fixed.

Correction to #5: Windows does support pread() - it's in ReadFile()'s OVERLAPPED parameter.

vi...@gmail.com <vi...@gmail.com> #7Jul 5, 2020 07:23AM

@7: we'd still need to write the pread wrapper, though. (similar if we went with mmap/munmap.)

https://android-review.googlesource.com/#/c/355481/ pre-sizes the vector, which should be enough to undo the regression from '.3 to '.4...

ch...@google.com <ch...@google.com> #8Jul 6, 2020 01:41AM

https://android-review.googlesource.com/355818 switches "adb sideload" over to lseek/read. the time difference isn't measurable, but the memory requirements are then down to just 64KiB.

vi...@gmail.com <vi...@gmail.com> #9Jul 8, 2020 07:46AM

Hi I'm getting the same issue on Windows 10 when I try to sideload a TWRP backup.
- adb devices gives my device
- adb usb gives error: closed
- adb sideload 6.13.771.4_ckpv5.zip gives
loading: '6.13.771.4_ckpv5.zip'...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

Please can somebody help with this issue I've been trying to sort this for 3 days. Thanks.

vi...@gmail.com <vi...@gmail.com> #10Oct 13, 2020 02:44AM

I also get this problem. Is there a workaround?

vi...@gmail.com <vi...@gmail.com> #11Jan 3, 2021 10:57AM

I also get this error message when trying to update Android OS 7.1.1 from N6F26R to N6F26U security patch for Nexus 6. Please help. Thank you.

ch...@google.com <ch...@google.com> #12Jan 5, 2021 02:40AM

It happens when i try to flash any rom to my OnePlus 3, how can i solve it?

vi...@gmail.com <vi...@gmail.com> #13Jan 8, 2021 07:48AM

Trying to sideload via adb on Win10 gives me this as well. Nexus 6 trying to sideload from 7.0 to 7.1.1 (N6F26U, Mar 2017)

ch...@google.com <ch...@google.com> #14Jan 8, 2021 10:09AM

Status: In Progress (Accepted) (reopened)

My Nexus 9 is on a bootloop and is locked so this was my way out of the bootloop but I've got the same error std::bad_alloc...
If someone has found a way to suppress this error let us know !

ap...@google.com <ap...@google.com> #15Jan 12, 2021 02:10AM

As this bug is in 25.0.4 only, simply revert to platform tools 25.0.3 to successfully sideload the image. This solved both my 'std::bad_alloc' error and bootloop error (hopefully).

ch...@google.com <ch...@google.com> #16Jan 12, 2021 02:49AM