From: Lynne <dev@lynne.ee>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 0/3] Fix memory leaks in vulkan ffv1 decoding
Date: Wed, 11 Jun 2025 13:30:46 +0900
Message-ID: <e2578f99-572d-4539-82db-a4dcc9e3f987@lynne.ee> (raw)
In-Reply-To: <20250610-vk-ffv1-leaks-v1-0-6bd045fc51e2@gmail.com>
On 11/06/2025 03:58, averne wrote:
> This fixes a few leaks reported by LeakSanitizer.
> I tested this on my Intel laptop running anv, with
> these patches no more leaks are detected.
>
> Signed-off-by: averne <averne381@gmail.com>
> ---
> averne (3):
> vulkan: fix leak in FFVkExecPool
> vulkan/ffv1dec: fix leak in FFVulkanDecodeShared
> vulkan/ffv1dec: fix FFVkSPIRVCompiler leak
>
> libavcodec/vulkan_ffv1.c | 60 ++++++++++++++++++++----------------------------
> libavutil/vulkan.c | 2 ++
> 2 files changed, 27 insertions(+), 35 deletions(-)
> ---
> base-commit: 4059bce713118f961d24b5f08a4881c5e7214f9b
> change-id: 20250610-vk-ffv1-leaks-7f0722236745
>
> Best regards,
LGTM
Thanks, pushed the patchset.
_______________________________________________
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".
prev parent reply other threads:[~2025-06-11 4:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 18:58 averne
2025-06-10 18:58 ` [FFmpeg-devel] [PATCH 1/3] vulkan: fix leak in FFVkExecPool averne
2025-06-10 18:58 ` [FFmpeg-devel] [PATCH 2/3] vulkan/ffv1dec: fix leak in FFVulkanDecodeShared averne
2025-06-10 18:58 ` [FFmpeg-devel] [PATCH 3/3] vulkan/ffv1dec: fix FFVkSPIRVCompiler leak averne
2025-06-11 4:30 ` Lynne [this message]
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=e2578f99-572d-4539-82db-a4dcc9e3f987@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