From: "Sven Strickroth via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Patrick Steinhardt <ps@pks.im>,
Sven Strickroth <email@cs-ware.de>,
Sven Strickroth <email@cs-ware.de>
Subject: [PATCH] repository: prevent memory leak when releasing ref stores
Date: Mon, 05 Aug 2024 10:56:04 +0000 [thread overview]
Message-ID: <pull.1758.git.git.1722855364436.gitgitgadget@gmail.com> (raw)
From: Sven Strickroth <email@cs-ware.de>
`ref_store_release` does not free the ref_store allocated in
`ref_store_init`.
Signed-off-by: Sven Strickroth <email@cs-ware.de>
---
repository: prevent memory leak when releasing ref stores
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1758%2Fcsware%2Frepository-memory-leak-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1758/csware/repository-memory-leak-v1
Pull-Request: https://github.com/git/git/pull/1758
repository.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/repository.c b/repository.c
index 9825a308993..46f1eadfe95 100644
--- a/repository.c
+++ b/repository.c
@@ -366,12 +366,16 @@ void repo_clear(struct repository *repo)
FREE_AND_NULL(repo->remote_state);
}
- strmap_for_each_entry(&repo->submodule_ref_stores, &iter, e)
+ strmap_for_each_entry(&repo->submodule_ref_stores, &iter, e) {
ref_store_release(e->value);
+ free(e->value);
+ }
strmap_clear(&repo->submodule_ref_stores, 1);
- strmap_for_each_entry(&repo->worktree_ref_stores, &iter, e)
+ strmap_for_each_entry(&repo->worktree_ref_stores, &iter, e) {
ref_store_release(e->value);
+ free(e->value);
+ }
strmap_clear(&repo->worktree_ref_stores, 1);
repo_clear_path_cache(&repo->cached_paths);
base-commit: e559c4bf1a306cf5814418d318cc0fea070da3c7
--
gitgitgadget
next reply other threads:[~2024-08-05 10:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 10:56 Sven Strickroth via GitGitGadget [this message]
2024-08-05 15:50 ` [PATCH] repository: prevent memory leak when releasing ref stores Sven Strickroth
2024-08-05 17:42 ` Junio C Hamano
2024-08-05 16:28 ` Junio C Hamano
2024-08-05 17:24 ` Junio C Hamano
2024-08-06 6:20 ` Patrick Steinhardt
2024-08-06 15:44 ` Junio C Hamano
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=pull.1758.git.git.1722855364436.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=email@cs-ware.de \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
/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).