VP9 decode report ref frame dimensions invalid

[yancen]

Summary of the bug:

I want to decode a vp9 file to yuv, ffmpeg report some error on decoding.
How to reproduce:

% ffmpeg -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -v verbose -i test.ivf -pix_fmt p010le -f rawvideo -vsync passthrough -vframes 110 -y dump.yuv

ffmpeg version N-93452-g8032c08f49 Copyright (c) 2000-2019 the FFmpeg developers
  built with gcc 7 (Ubuntu 7.4.0-1ubuntu1~18.04)
  configuration: --enable-shared --enable-gpl --enable-libx264 --enable-debug --extra-cflags=-g --extra-ldflags=-g --enable-version3 --enable-vaapi --enable-libvpx

Platform: Kaby Lake and Gemini Lake
Arch: x86_64
Kernel: 4.15.0-20-generic
Libva: 382acf177ce18c069e0293408afa34c5875296ff
libva-utils: 375e4eaae3377c1806e83874f9fa9b79b1f225b1
ffmpeg-vaapi: b8ebce4f84b653b8a50a23398e3d12a607b5cddb (master branch)

Error message:
Error while decoding stream #0:0: Input/output error
[vp9 @ 0x5558a2e7d4c0] Invalid ref frame dimensions 1920x551 for frame size 333x411
Error while decoding stream #0:0: Input/output error
Error while decoding stream #0:0: Invalid data found when processing input
[vp9 @ 0x5558a2e85800] Invalid ref frame dimensions 326x917 for frame size 259x373
Error while decoding stream #0:0: Invalid data found when processing input
No more output streams to write to, finishing.

[James]

You need to provide the sample that's failing.

Does it also fail with current git master? b8ebce4f84b653b8a50a23398e3d12a607b5cddb is old, and 8032c08f49 does not exist.

[Carl Eugen Hoyos]

Please reopen this ticket if you can provide the failing input file.