New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 696015 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug

Blocked on:
issue 726392



Sign in to add a comment

MediaCodec: Codec reported err 0x80001009

Project Member Reported by xhw...@chromium.org, Feb 24 2017

Issue description

Chrome Version: ToT
OS: Android M
Device: N7v2

What steps will reproduce the problem?
(1) Patch https://chromiumcodereview.appspot.com/2707393002/
(2) Build and install Clank
(3) build/android/adb_run_chrome_public "https://transitionbug-dot-shaka-player-demo.appspot.com/demo/?lang=en-AU\;play"
(4) seek anywhere before 10:00 minute
(5) repeat (4)

What is the expected result?
Playback and seek works.

What happens instead?
Crash in MediaCodec. See attached log file for full log.

02-24 13:08:11.588 20500 22514 E         : 
02-24 13:08:11.588 20500 22514 E         :  not in avi mode
02-24 13:08:12.580 20500 22514 E OMX-VDEC-1080P: 
02-24 13:08:12.580 20500 22514 E OMX-VDEC-1080P:  OMX_COMPONENT_GENERATE_HARDWARE_ERROR
02-24 13:08:12.580 20500 22514 E OMX-VDEC-1080P: 
02-24 13:08:12.580 20500 22514 E OMX-VDEC-1080P: ERROR: Sending OMX_EventError to Client
02-24 13:08:12.580 20500 22514 E OMX-VDEC-1080P: 
02-24 13:08:12.580 20500 22514 E OMX-VDEC-1080P:  WARNING: Unexpected flush from driver
02-24 13:08:12.580 20500 22514 E OMX-VDEC-1080P: 
02-24 13:08:12.580 20500 22514 E OMX-VDEC-1080P:  WARNING: Unexpected flush from driver
02-24 13:08:12.580 22369 22511 E ACodec  : [OMX.qcom.video.decoder.avc] ERROR(0x80001009)
02-24 13:08:12.580 22369 22511 E ACodec  : signalError(omxError 0x80001009, internalError -2147483648)
02-24 13:08:12.580 22369 22510 E MediaCodec: Codec reported err 0x80001009, actionCode 0, while in state 6
02-24 13:08:12.588 22369 22383 E cr_MediaCodecBridge: Failed to dequeue input buffer
02-24 13:08:12.588 22369 22383 E cr_MediaCodecBridge: java.lang.IllegalStateException
02-24 13:08:12.588 22369 22383 E cr_MediaCodecBridge:   at android.media.MediaCodec.native_dequeueInputBuffer(Native Method)
02-24 13:08:12.588 22369 22383 E cr_MediaCodecBridge:   at android.media.MediaCodec.dequeueInputBuffer(MediaCodec.java:2319)
02-24 13:08:12.588 22369 22383 E cr_MediaCodecBridge:   at org.chromium.media.MediaCodecBridge.dequeueInputBuffer(MediaCodecBridge.java:275)
02-24 13:08:12.588 22369 22383 E cr_MediaCodecBridge:   at org.chromium.content.app.ContentMain.nativeStart(Native Method)
02-24 13:08:12.588 22369 22383 E cr_MediaCodecBridge:   at org.chromium.content.app.ContentMain.start(ContentMain.java:27)
02-24 13:08:12.588 22369 22383 E cr_MediaCodecBridge:   at org.chromium.content.app.ChildProcessServiceImpl$2.run(ChildProcessServiceImpl.java:280)
02-24 13:08:12.588 22369 22383 E cr_MediaCodecBridge:   at java.lang.Thread.run(Thread.java:818)
02-24 13:08:12.588 22369 22383 E chromium: [ERROR:android_video_decode_accelerator.cc(498)] DequeueInputBuffer failed
02-24 13:08:12.589 22326 22505 V chromium: [VERBOSE1:decoder_stream.cc(441)] OnDecodeDone<video>: Decode error!
02-24 13:08:12.589 22326 22505 E chromium: [ERROR:render_media_log.cc(30)] MediaEvent: MEDIA_ERROR_LOG_ENTRY {"error":"video decode error"}
02-24 13:08:12.589 22326 22505 E chromium: [ERROR:gpu_video_decoder.cc(886)] VDA Error: 4
02-24 13:08:12.598 22369 22508 W cr_MediaCodecBridge: Releasing: OMX.qcom.video.decoder.avc
02-24 13:08:12.607 22326 22342 E chromium: [ERROR:render_media_log.cc(30)] MediaEvent: PIPELINE_ERROR pipeline: decode error
 
media_codec_error.txt
107 KB View Download

Comment 1 by w...@chromium.org, Feb 24 2017

Hmm, I couldn't repro after seeking around 12 times on a Pixel tablet with Android N.

Can't play the video on a N7v2 running KK. I get Shaka Error DRM.LICENSE_REQUEST_FAILURE.
Make sure you're using 4.4.2 or whatever the top kk version is.

Comment 3 by w...@chromium.org, Feb 24 2017

It was 4.4, api level 19. I see in the logs we actually get to trying to queue a buffer to MediaCodec, but we get back NO_KEY.
EME doesn't work on early kitkat versions; hence the 4.4.2 need

Comment 5 by w...@chromium.org, Feb 24 2017

Oops, meant to write 4.4.4!

Comment 7 by xhw...@chromium.org, Feb 25 2017

The first 10 minutes of the video should be clear. When did you see the NO_KEY?

Comment 8 by dskiba@chromium.org, May 25 2017

Blockedon: 726392
Project Member

Comment 9 by sheriffbot@chromium.org, May 28 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: liber...@chromium.org
liberato@ anything to do here?
Status: WontFix (was: Untriaged)
i don't think so.

i don't think that we can fix the underlying error, unfortunately, based on what we have.

we now catch a generic exception in MediaCodecBridge, so at least it shouldn't crash anymore.

Sign in to add a comment