From: cgit at cryptocrack.de (Lukas Fleischer)
Subject: [PATCH 0/6] Fix several obvious memory leaks
Date: Mon, 4 Mar 2013 13:25:32 +0100 [thread overview]
Message-ID: <1362399938-20209-1-git-send-email-cgit@cryptocrack.de> (raw)
This is far from complete but fixes a couple of obvious memory leaks
seen when running `PATH_INFO=/cgit/[...]/ ./cgit` using valgrind.
In particular, this fixes all "definitely lost" block seen with:
* /cgit/refs/
* /cgit/tree/
* /cgit/commit/
* /cgit/diff/
Lukas Fleischer (6):
Free reflists after usage
print_tag_downloads(): Free ref variable
find_default_branch(): Free refmatch after usage
cgit_print_tree(): Free curr_rev after usage
cgit_print_commit(): Free tmp variable
cgit_print_snapshot_links(): Free prefix variable
cgit.c | 8 ++++++++
cgit.h | 1 +
shared.c | 36 ++++++++++++++++++++++++++++++++++++
ui-commit.c | 1 +
ui-refs.c | 12 +++++++++++-
ui-shared.c | 1 +
ui-tree.c | 5 ++++-
7 files changed, 62 insertions(+), 2 deletions(-)
--
1.8.2.rc0.247.g811e0c0
next reply other threads:[~2013-03-04 12:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 12:25 cgit [this message]
2013-03-04 12:25 ` [PATCH 1/6] Free reflists after usage cgit
2013-03-04 12:25 ` [PATCH 2/6] print_tag_downloads(): Free ref variable cgit
2013-03-04 12:25 ` [PATCH 3/6] find_default_branch(): Free refmatch after usage cgit
2013-03-04 12:25 ` [PATCH 4/6] cgit_print_tree(): Free curr_rev " cgit
2013-03-05 1:36 ` Jason
2013-03-04 12:25 ` [PATCH 5/6] cgit_print_commit(): Free tmp variable cgit
2013-03-04 12:25 ` [PATCH 6/6] cgit_print_snapshot_links(): Free prefix variable cgit
2013-03-05 0:53 ` [PATCH 0/6] Fix several obvious memory leaks Jason
2013-03-05 1:50 ` Jason
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=1362399938-20209-1-git-send-email-cgit@cryptocrack.de \
--to=cgit@lists.zx2c4.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 NNTP newsgroup(s).