From: Florian Weimer <fweimer@redhat.com>
To: Parthiban <parthiban@linumiz.com>
Cc: libc-help@sourceware.org
Subject: Re: glibc mq_notify memory leak report
Date: Mon, 09 Jan 2023 18:11:43 +0100 [thread overview]
Message-ID: <87wn5viqeo.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <abe21391-8d9f-4035-f0a5-d4f8a1a7d83f@linumiz.com> (parthiban@linumiz.com's message of "Mon, 9 Jan 2023 20:43:13 +0530")
* > Dear All,
>
> I have the following code snippet and `mq_close`, `mq_unlink` is
> called in exit path. But with valgrind, I have the summary about
> possibly lost.
>
> How to gracefully remove the notification during exit path?
I think this is the same issue that was reported here for timer_create
(which also has a helper thread):
libc timer_create with option SIGEV_THREAD system call having memory
leaks after timer_delete system call
<https://sourceware.org/bugzilla/show_bug.cgi?id=29705>
I don't think there is a good way to fix this. It's not an unbounded
leak, so it does not impact the application while it runs.
Thanks,
Florian
prev parent reply other threads:[~2023-01-09 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 15:13 Parthiban
2023-01-09 17:11 ` Florian Weimer [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=87wn5viqeo.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-help@sourceware.org \
--cc=parthiban@linumiz.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).