[FFmpeg-trac] #7687(avcodec:new): h264_omx can stall due to not handling fragmented frames correctly
FFmpeg
trac at avcodec.org
Thu Jan 17 19:00:17 EET 2019
#7687: h264_omx can stall due to not handling fragmented frames correctly
---------------------------------------+-----------------------------------
Reporter: 6by9 | Owner:
Type: defect | Status: new
Priority: normal | Component: avcodec
Version: git-master | Resolution:
Keywords: h264_omx, omx | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
---------------------------------------+-----------------------------------
Comment (by 6by9):
> Isn’t this a duplicate of ticket #6586?
No. #6586 is the zerocopy path of h264_omx passing a pointer into IL that
has issues in VCHIQ
The buffer is allocated by V4L2, mmaped into userspace results with flags
VM_IO and/or VM_PFNMAP. VCHIQ then tries to pass that to the GPU on behalf
of IL and get_user_pages fails.
https://github.com/raspberrypi/firmware/issues/851
I'm 99.9% certain that is a VCHIQ kernel driver issue - FFmpeg is in the
clear.
This issue is FFmpeg mishandling fragmented buffers on the output side.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/7687#comment:3>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list