From: fdanis-oss <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 223814: device: Fix memory leak
Date: Wed, 18 Jun 2025 15:35:34 +0000 (UTC) [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/973494/000000-223814@github.com> (raw)
Branch: refs/heads/973494
Home: https://github.com/bluez/bluez
Commit: 223814198364497e444fe1b49b81ae0c16137302
https://github.com/bluez/bluez/commit/223814198364497e444fe1b49b81ae0c16137302
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2025-06-18 (Wed, 18 Jun 2025)
Changed paths:
M src/device.c
Log Message:
-----------
device: Fix memory leak
This frees the LastUsedBearer string to avoid memory leak:
Direct leak of 12 byte(s) in 2 object(s) allocated from:
#0 0x7ccf538fd9c7 in malloc ../../../../src/libsanitizer/asan/
asan_malloc_linux.cpp:69
#1 0x7ccf53665b09 in g_malloc (/lib/x86_64-linux-gnu/
libglib-2.0.so.0+0x62b09)
#2 0x7ccf53659b90 (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x56b90)
#3 0x7ccf53659cd4 in g_key_file_get_string (/lib/x86_64-linux-gnu/
libglib-2.0.so.0+0x56cd4)
#4 0x5c8c691f2811 in load_info src/device.c:4225
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-06-18 15:35 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=bluez/bluez/push/refs/heads/973494/000000-223814@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@vger.kernel.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).