[FFmpeg-trac] #6642(ffmpeg:new): GPU hang in decoding hevc video by using ffmpeg
FFmpeg
trac at avcodec.org
Fri Sep 8 22:30:36 EEST 2017
#6642: GPU hang in decoding hevc video by using ffmpeg
------------------------------------+----------------------------------
Reporter: hsyrja | Owner:
Type: defect | Status: new
Priority: normal | Component: ffmpeg
Version: git-master | Resolution:
Keywords: | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
------------------------------------+----------------------------------
Comment (by jkqxz):
To make clearer that other platforms are fine:
{{{
$ ./ffmpeg_g -v 0 -y -i hang.vid out_sw.yuv
$ ./ffmpeg_g -v 0 -y -hwaccel vaapi -hwaccel_device /dev/dri/renderD129 -i
hang.vid -vf format=yuv420p out_amd.yuv
libva info: VA-API version 0.40.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/local/lib/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_0_40
libva info: va_openDriver() returns 0
$ ls -l out_*.yuv
-rw-r--r-- 1 mrt mrt 388454400 Sep 8 20:23 out_amd.yuv
-rw-r--r-- 1 mrt mrt 388454400 Sep 8 20:23 out_sw.yuv
$ cmp out_sw.yuv out_amd.yuv
$
}}}
i.e. output is bit-identical, so VAAPI is not the problem.
Then:
{{{
$ ./ffmpeg_g -v 0 -y -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -i
hang.vid -vf format=yuv420p out_intel.yuv
libva info: VA-API version 0.40.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/local/lib/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_40
libva info: va_openDriver() returns 0
}}}
and the GPU hangs immediately.
(renderD128 is an Intel Skylake GT2, renderD129 is an AMD Polaris 11.)
--
Ticket URL: <https://trac.ffmpeg.org/ticket/6642#comment:3>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list