[FFmpeg-trac] #6642(ffmpeg:new): GPU hang in decoding hevc video by using ffmpeg
FFmpeg
trac at avcodec.org
Fri Sep 8 10:30:58 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 hsyrja):
From Libya team.
I saw lots of error messages when using a tool to parse hang.vid
I can't reproduce this issue with gstreamer-vaapi, it seems ffmpeg and
gstreamer handle the element errors in different way so they pass
different picture parameters and slice parameters to the driver. You may
enable VA tracer by setting LIBVA_TRACE in your environment then check the
tracer log.
e.g. in gstreamer
[48642.979908][ctx 0x02000000] pcm_sample_bit_depth_luma_minus1 = 0
[48642.979909][ctx 0x02000000] pcm_sample_bit_depth_chroma_minus1 = 0
...
[48642.979952][ctx 0x02000000] slice_parsing_fields = 15246
however in FFmpeg
[48794.782034][ctx 0x02000000] pcm_sample_bit_depth_luma_minus1 = 255
[48794.782034][ctx 0x02000000] pcm_sample_bit_depth_chroma_minus1 = 255
...
[48794.782054][ctx 0x02000000] slice_parsing_fields = 910
According to the tracer log, I think this is a FFmpeg specific issue.
driver(HW) provides error handling, but it can't cover all of errors.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/6642#comment:1>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list