From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: Clean up glib / GKeyFile memory use
Date: Sat, 6 Mar 2021 09:49:30 -0400 [thread overview]
Message-ID: <20210306134934.491249-1-david@tethera.net> (raw)
It turns out I was too optimistic / lazy about how the g_key_file API
manages memory. None of the resulting memory leaks are large (unless
you somehow keep War and Peace in your config file), but it is more
tidy to clean them up, and makes it easier to spot more significant
leaks in the already noisy output from valgrind.
This series applies on top of master. I'll have to rebase the other
config series on top (and possibly clean up a few more glib related
memory leaks).
next reply other threads:[~2021-03-06 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 13:49 David Bremner [this message]
2021-03-06 13:49 ` [PATCH 1/4] lib/open: use local talloc context in n_d_create_with_config David Bremner
2021-03-06 13:49 ` [PATCH 2/4] lib/open: free value from g_key_file_get_value David Bremner
2021-03-06 13:49 ` [PATCH 3/4] lib/config: free memory from traversing GKeyFile David Bremner
2021-03-06 13:49 ` [PATCH 4/4] lib/open: free GKeyFile David Bremner
2021-03-14 12:53 ` Clean up glib / GKeyFile memory use David Bremner
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210306134934.491249-1-david@tethera.net \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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).