From: Lynne <dev@lynne.ee>
To: Ffmpeg Devel <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] [PATCH] vulkan_decode: check if yuv_sampler exists before freeing it
Date: Mon, 29 May 2023 02:22:34 +0200 (CEST)
Message-ID: <NWZse6z--3-9@lynne.ee> (raw)
[-- Attachment #1: Type: text/plain, Size: 131 bytes --]
No Vulkan function is NULL-safe, for no real reason, despite
the language defining and returning VK_NULL_HANDLE.
Patch attached.
[-- Attachment #2: 0001-vulkan_decode-check-if-yuv_sampler-exists-before-fre.patch --]
[-- Type: text/x-diff, Size: 1057 bytes --]
From 60f73541330ae33f92b862250e7f3c928394c0b9 Mon Sep 17 00:00:00 2001
From: Lynne <dev@lynne.ee>
Date: Mon, 29 May 2023 02:04:59 +0200
Subject: [PATCH] vulkan_decode: check if yuv_sampler exists before freeing it
No Vulkan function is NULL-safe, for no real reason, despite
the language defining and returning VK_NULL_HANDLE.
---
libavcodec/vulkan_decode.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/libavcodec/vulkan_decode.c b/libavcodec/vulkan_decode.c
index 1d1fb9ad97..6138106fef 100644
--- a/libavcodec/vulkan_decode.c
+++ b/libavcodec/vulkan_decode.c
@@ -581,8 +581,9 @@ static void free_common(void *opaque, uint8_t *data)
ff_vk_video_common_uninit(s, &ctx->common);
- vk->DestroySamplerYcbcrConversion(s->hwctx->act_dev, ctx->yuv_sampler,
- s->hwctx->alloc);
+ if (ctx->yuv_sampler)
+ vk->DestroySamplerYcbcrConversion(s->hwctx->act_dev, ctx->yuv_sampler,
+ s->hwctx->alloc);
ff_vk_uninit(s);
}
--
2.40.1
[-- Attachment #3: Type: text/plain, Size: 251 bytes --]
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next reply other threads:[~2023-05-29 0:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 0:22 Lynne [this message]
2023-05-29 1:20 ` Philip Langdale
2023-05-29 1:32 ` Lynne
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=NWZse6z--3-9@lynne.ee \
--to=dev@lynne.ee \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git