Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Tim Blechmann via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Tim Blechmann <tim.blechmann@qt.io>
Subject: [FFmpeg-devel] [PATCH] libavutil: fix memory leak of drmVersion
Date: Wed, 25 Jun 2025 10:26:16 +0800
Message-ID: <mailman.4334.1750818394.1384.ffmpeg-devel@ffmpeg.org> (raw)

[-- Attachment #1: Type: message/rfc822, Size: 11825 bytes --]

From: Tim Blechmann <tim.blechmann@qt.io>
To: ffmpeg-devel@ffmpeg.org
Subject: [PATCH] libavutil: fix memory leak of drmVersion
Date: Wed, 25 Jun 2025 10:26:16 +0800
Message-ID: <283506b9-e603-4753-bba4-9b1b27a5916a@qt.io>

address sanitizer showed some leaks of drmVersion structs.
`vaapi_device_create` did not call drmFreeVersion in all possible code
paths.

Signed-off-by: Tim Blechmann <tim.blechmann@qt.io>
---
  libavutil/hwcontext_vaapi.c | 3 +++
  1 file changed, 3 insertions(+)

diff --git a/libavutil/hwcontext_vaapi.c b/libavutil/hwcontext_vaapi.c
index 95aa38d9d2..92b704891e 100644
--- a/libavutil/hwcontext_vaapi.c
+++ b/libavutil/hwcontext_vaapi.c
@@ -1810,30 +1810,33 @@ static int vaapi_device_create(AVHWDeviceContext *ctx, const char *device,
                      char drm_vendor[8];
                      if (drmGetDevice(priv->drm_fd, &device)) {
                          av_log(ctx, AV_LOG_VERBOSE,
                                 "Failed to get DRM device info for device %d.\n", n);
                          close(priv->drm_fd);
                          priv->drm_fd = -1;
+                        drmFreeVersion(info);
                          continue;
                      }
                       snprintf(drm_vendor, sizeof(drm_vendor), "0x%x", 
device->deviceinfo.pci->vendor_id);
                      if (strcmp(vendor_id->value, drm_vendor)) {
                          av_log(ctx, AV_LOG_VERBOSE, "Ignoring device %d "
                                 "with non-matching vendor id (%s).\n",
                                 n, vendor_id->value);
                          drmFreeDevice(&device);
                          close(priv->drm_fd);
                          priv->drm_fd = -1;
+                        drmFreeVersion(info);
                          continue;
                      }
                      av_log(ctx, AV_LOG_VERBOSE, "Trying to use "
                             "DRM render node for device %d, "
                             "with matching vendor id (%s).\n",
                             n, vendor_id->value);
                      drmFreeDevice(&device);
+                    drmFreeVersion(info);
                      break;
                  }
                  drmFreeVersion(info);
  #endif
                  av_log(ctx, AV_LOG_VERBOSE, "Trying to use "
                         "DRM render node for device %d.\n", n);
-- 
2.48.1


[-- Attachment #2: 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".

                 reply	other threads:[~2025-06-25  2:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=mailman.4334.1750818394.1384.ffmpeg-devel@ffmpeg.org \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=tim.blechmann@qt.io \
    /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