Opened 3 months ago

Last modified 3 weeks ago

#7723 new defect

[FFmpeg-vaapi][vp8 decode] Failed to end picture decode issue: 23 (internal decoding error)

Reported by: andreyor Owned by:
Priority: normal Component: undetermined
Version: git-master Keywords: vaapi
Cc: eero.t.tamminen@intel.com, zhong.li@intel.com, ullysses.a.eoff@intel.com Blocked By:
Blocking: Reproduced by developer: no
Analyzed by developer: no

Description

How to reproduce:

ffmpeg -y -hwaccel vaapi -vaapi_device /dev/dri/renderD128 -hwaccel_output_format vaapi -i <input> -frames 250 -f null -

ffmpeg version N-93001-g87c165c237

Output:

[vp8 @ 0x55c14b3bea40] Failed to end picture decode issue: 23 (internal decoding error).
 Error while decoding stream #0:0: Input/output error
 [vp8 @ 0x55c14b3a7e80] Failed to end picture decode issue: 23 (internal decoding error).
 Error while decoding stream #0:0: Input/output error
     Last message repeated 1 times
 Impossible to convert between the formats supported by the filter 'Parsed_null_0' and the filter 'auto_scaler_0'
 Error reinitializing filters!
 Failed to inject frame into filter network: Function not implemented
 Error while processing the decoded data for stream #0:0

Change History (11)

comment:1 Changed 3 months ago by cehoyos

  • Component changed from ffmpeg to undetermined
  • Keywords vaapi added; ffmpeg-vaapi removed
  • Priority changed from important to normal

Why do you believe this is an issue that can be fixed in FFmpeg?

comment:2 Changed 3 months ago by cehoyos

Please provide your input sample.

comment:3 Changed 2 months ago by andreyor

Input streams:
http://fate-suite.ffmpeg.org/vp8/

Full output log:

ffmpeg -y -hwaccel vaapi -vaapi_device /dev/dri/renderD128 -hwaccel_output_format vaapi -i dash_video4.webm -frames 250 -f null -
ffmpeg version N-93064-ged20fbcd48 Copyright (c) 2000-2019 the FFmpeg developers
  built with gcc 7 (Ubuntu 7.3.0-27ubuntu1~18.04)
  configuration: --prefix=/msdk/FFmpeg/ffmpeg_build --enable-libmfx
  libavutil      56. 26.100 / 56. 26.100
  libavcodec     58. 46.100 / 58. 46.100
  libavformat    58. 26.100 / 58. 26.100
  libavdevice    58.  6.101 / 58.  6.101
  libavfilter     7. 48.100 /  7. 48.100
  libswscale      5.  4.100 /  5.  4.100
  libswresample   3.  4.100 /  3.  4.100
Input #0, matroska,webm, from 'dash_video4.webm':
  Metadata:
    encoder         : Lavf56.7.101
  Duration: 00:00:32.48, start: 0.000000, bitrate: 214 kb/s
    Stream #0:0(eng): Video: vp8, yuv420p(progressive), 320x240, SAR 255:191 DAR 340:191, 25 fps, 25 tbr, 1k tbn, 1k tbc (default)
Stream mapping:
  Stream #0:0 -> #0:0 (vp8 (native) -> wrapped_avframe (native))
Press [q] to stop, [?] for help
[vp8 @ 0x55a72f77c280] Failed to end picture decode issue: 23 (internal decoding error).
[vp8 @ 0x55a72f77f380] Failed to end picture decode issue: 23 (internal decoding error).
[vp8 @ 0x55a72f782440] Failed to end picture decode issue: 23 (internal decoding error).
[vp8 @ 0x55a72f785580] Failed to end picture decode issue: 23 (internal decoding error).
[vp8 @ 0x55a72f788640] Failed to end picture decode issue: 23 (internal decoding error).
[vp8 @ 0x55a72f78b780] Failed to end picture decode issue: 23 (internal decoding error).
[vp8 @ 0x55a72f78e840] Failed to end picture decode issue: 23 (internal decoding error).
Output #0, null, to 'pipe:':
  Metadata:
    encoder         : Lavf58.26.100
    Stream #0:0(eng): Video: wrapped_avframe, vaapi_vld, 320x240 [SAR 255:191 DAR 340:191], q=2-31, 200 kb/s, 25 fps, 25 tbn, 25 tbc (default)
    Metadata:
      encoder         : Lavc58.46.100 wrapped_avframe
Error while decoding stream #0:0: Input/output error
[vp8 @ 0x55a72f791980] Failed to end picture decode issue: 23 (internal decoding error).
Error while decoding stream #0:0: Input/output error
[vp8 @ 0x55a72f77ac00] Failed to end picture decode issue: 23 (internal decoding error).
[vp8 @ 0x55a72f77c280] Failed to end picture decode issue: 23 (internal decoding error).
Error while decoding stream #0:0: Input/output error
[vp8 @ 0x55a72f77f380] Failed to end picture decode issue: 23 (internal decoding error).
Error while decoding stream #0:0: Input/output error
[vp8 @ 0x55a72f782440] Failed to end picture decode issue: 23 (internal decoding error).
Error while decoding stream #0:0: Input/output error
[vp8 @ 0x55a72f785580] Failed to end picture decode issue: 23 (internal decoding error).
Error while decoding stream #0:0: Input/output error
[vp8 @ 0x55a72f788640] Failed to end picture decode issue: 23 (internal decoding error).
Error while decoding stream #0:0: Input/output error
    Last message repeated 7 times
Impossible to convert between the formats supported by the filter 'Parsed_null_0' and the filter 'auto_scaler_0'
Error reinitializing filters!
Failed to inject frame into filter network: Function not implemented
Error while processing the decoded data for stream #0:0
Conversion failed!

comment:4 follow-up: Changed 2 months ago by cehoyos

How do you know that this is not a driver issue?

comment:5 in reply to: ↑ 4 Changed 8 weeks ago by eero-t

  • Cc eero.t.tamminen@intel.com added

Replying to cehoyos:

How do you know that this is not a driver issue?

That's a good question as there are many issues listed for VP8 e.g. in the iHD media-driver issue tracker:
https://github.com/intel/media-driver/issues/

Many of them were fixed by end of last year, but some are still open.

Reporter doesn't state which HW he's using and with which VAAPI driver; i965, iHD... Nor what was the version of the driver used. I think this bug report is invalid without the driver info.

comment:6 Changed 7 weeks ago by lizhong1008

  • Cc zhong.li@intel.com added

Can reproduce this issue with commit 9326117bf6.
This is a multithread issue, if set "thread=1" then the error dispears:
ffmpeg -y -hwaccel vaapi -hwaccel_output_format vaapi -threads 1 -i /fate-suite/vp8/dash_video4.webm -frames 250 -f null -

a iHD driver issue has been created to check it, as the same time there was a ffmpeg patch to fix it(https://patchwork.ffmpeg.org/patch/9943/) but still not merged.

comment:8 in reply to: ↑ 7 Changed 6 weeks ago by lizhong1008

Replying to andreyor:

Ok, thanks. Just for information - it still reproducible on the latest stack:

Sure, It definitely existed since https://patchwork.ffmpeg.org/patch/9943/ is not merged.
Two options:

  1. Use single thread via set "thread=1" in your command line.
  2. Or you can wait https://patchwork.ffmpeg.org/patch/9943/ applied or apply it to yourself project.

comment:9 follow-up: Changed 6 weeks ago by andreyor

Thanks, also, could you please post the iHD driver issue, that you have mentioned ?

Last edited 6 weeks ago by andreyor (previous) (diff)

comment:10 in reply to: ↑ 9 Changed 6 weeks ago by lizhong1008

Replying to andreyor:

Thanks, also, could you please post the iHD driver issue, that you have mentioned ?

Yes, it has also been checked on iHD driver side: https://github.com/intel/media-driver/issues/317 and https://github.com/intel/media-driver/issues/190. But looks like should be fixed in ffmpeg level with ​https://patchwork.ffmpeg.org/patch/9943/.

comment:11 Changed 3 weeks ago by uartie

  • Cc ullysses.a.eoff@intel.com added

https://patchwork.ffmpeg.org/patch/9943/ has been superseded by https://patchwork.ffmpeg.org/patch/10695/. This patch was submitted ~6 months ago (Oct 2018) but has received no reviews and lost momentum. @lizhong1008 can you review it?

Note: See TracTickets for help on using tickets.