PR #20286 opened by vytskalt
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20286
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20286.patch
Same as #20084
Turns out there were 2 more cases of this that I missed in the last PR
>From 8e489937f98aaaf4ee24fe448799fe1ce1057b12 Mon Sep 17
From: vytskalt
If ff_vk_exec_discard_deps is not called after ff_vk_exec_add_dep_frame
we get a reference cycle causing the frames context to never be freed.
Same situation as in 74e27d9e3182d2d256d11bb0d5d45633b054bbcb
Signed-off-by: vytskalt
---
libavutil/hwcontext_vulkan.c | 6 +-
1 fi
From: vytskalt
VK_QUEUE_FAMILY_IGNORED is only valid when the image is in CONCURRENT
sharing mode. When there is only one queue family it's in the EXCLUSIVE
sharing mode and the dst queue family must match it.
Fixes validation error during drm->vulkan frame mapping:
"pDependencyInfo->pImageMemor
