[FFmpeg-trac] #9967(avutil:new): [vaapi] av_hwframe_map with AV_PIX_FMT_PRIME_FD calls vaExportSurfaceHandle, but not vaSyncSurface

[FFmpeg]

#9967: [vaapi] av_hwframe_map with AV_PIX_FMT_PRIME_FD calls
vaExportSurfaceHandle, but not vaSyncSurface
----------------------------------+---------------------------------------
             Reporter:  goffioul  |                     Type:  enhancement
               Status:  new       |                 Priority:  normal
            Component:  avutil    |                  Version:
             Keywords:            |               Blocked By:
             Blocking:            |  Reproduced by developer:  0
Analyzed by developer:  0         |
----------------------------------+---------------------------------------
 When mapping a VA-API frame with av_hwframe_map and AV_PIX_FMT_PRIME_FD,
 vaExportSurfaceHandle is called to create the file descriptor, but it does
 not call vaSyncSurface. As a result, mmap'ing the file descriptor and
 reading from it may not yield correct result and lead to tearing artefact.

 Technically, the client app could probably call vaSyncSurface itself, but
 that would require accessing internals of ffmpeg, e.g. to access the VA
 display. It would be cleaner if the VA-API bits were entirely managed by
 ffmpeg.
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/9967>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker