ExoPlaybackException - MediaCodecVideoDecoderException

[Gitogitos]

Checklist

• I am able to reproduce the bug with the latest version.
• I made sure that there are no existing issues - open or closed - which I could contribute my information to.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Affected version

0.22.1

Steps to reproduce the bug

When I play YouTube, with video rotation sometimes without video rotation

Expected behavior

The video should play

Actual behavior

It's stop with error message

Screenshots/Screen recordings

No response

Logs

Exception

• User Action: play stream
• Request: Player error[type=1] occurred while playing https://www.youtube.com/watch?v=qrIDMfPRF6I
• Content Country: PL
• Content Language: pl-PL
• App Language: pl_PL
• Service: YouTube
• Version: 0.22.0 and 0.22.1
• OS: Linux motorola/athene/athene:7.0/NPJ25.93-14/16:user/release-keys 7.0 - 24

Crash log

com.google.android.exoplayer2.ExoPlaybackException: MediaCodecVideoRenderer error, index=0, format=Format(1, null, null, video/avc, avc1.64001F, -1, null, [1280, 720, 30.0], [-1, -1]), format_supported=YES
	at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:555)
	at android.os.Handler.dispatchMessage(Handler.java:98)
	at android.os.Looper.loop(Looper.java:154)
	at android.os.HandlerThread.run(HandlerThread.java:61)
Caused by: com.google.android.exoplayer2.video.MediaCodecVideoDecoderException: Decoder failed: OMX.qcom.video.decoder.avc
	at com.google.android.exoplayer2.video.MediaCodecVideoRenderer.createDecoderException(MediaCodecVideoRenderer.java:1410)
	at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.render(MediaCodecRenderer.java:864)
	at com.google.android.exoplayer2.ExoPlayerImplInternal.doSomeWork(ExoPlayerImplInternal.java:945)
	at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:478)
	... 3 more
Caused by: java.lang.IllegalStateException
	at android.media.MediaCodec.native_dequeueInputBuffer(Native Method)
	at android.media.MediaCodec.dequeueInputBuffer(MediaCodec.java:2513)
	at com.google.android.exoplayer2.mediacodec.SynchronousMediaCodecAdapter.dequeueInputBufferIndex(SynchronousMediaCodecAdapter.java:93)
	at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.feedInputBuffer(MediaCodecRenderer.java:1209)
	at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.render(MediaCodecRenderer.java:845)
	... 5 more

---

Affected Android/Custom ROM version

Android 7.0

Affected device model

Motorola Moto G4

Additional information

[litetex]

I think I have to clarify this exceptions a bit:
Whenever you encounter a ExoPlaybackException - MediaCodecVideoDecoderException it's usually a hardware/Exoplayer problem (like e.g. a GPU error on your PC) as can be seen in the stacktrace android.media.MediaCodec.native_dequeueInputBuffer(Native Method).
AFAIK there is nothing we can change/fix here.

This is only more often reported recently due to #7482 (before there was simply a toast saying Unexpected error and you couldn't report it).

[litetex]

I think we need a better error handling if such a problem occurs. All few days a new issue pops up that describes this or a similar problem related to MediaCodec

[watashibeme]

Once there used to be an option in android to whether use exo or not in developer options, it's annoying the hell out of me, exiting the player , recovering from player error, changing orientation, again, pause midway, again
Aaaaaaaaaaaaaaaa
Android 13, CrDroid 9
MicroG

[opusforlife2]

Android 13, CrDroid 9

@watashibeme crDroid is a known culprit for many player-related bugs. I highly suggest you use some other, more stable ROM like LOS.

[watashibeme]

Oh, so you know🤣
I would use LOS if it had some sort of customization section.
But I get your point, I'll think about it

[Dan-TBA]

sooo, whats the solution?

[opusforlife2]

AFAIK there is nothing we can change/fix here.

I think we need a better error handling if such a problem occurs.

Apart from this, the solution is to try switching to a non-buggy OS/device.

[tranquil222]

I fixed this on my tablet by changing the default resolution to1080p instead of 2160p. The higher resolution made it crash with this error code for some reason.