git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] Fix memory leak in get_reachable_subset

From
Mike Hommey <mh@glandium.org>
Date
Jun 3, 2023, 00:28 UTC
Message-ID
<20230603002819.1122129-1-mh@glandium.org>
Signed-off-by: Mike Hommey <mh@glandium.org>
---
 commit-reach.c | 2 ++
 1 file changed, 2 insertions(+)
diff --git a/commit-reach.c b/commit-reach.c
index 70bde8af05..f15d84566b 100644
--- a/commit-reach.c
+++ b/commit-reach.c
@@ -944,6 +944,8 @@ struct commit_list *get_reachable_subset(struct commit **from, int nr_from,
 		}
 	}
 
+	clear_prio_queue(&queue);
+
 	clear_commit_marks_many(nr_to, to, PARENT1);
 	clear_commit_marks_many(nr_from, from, PARENT2);
 
-- 
2.41.0.6.ge371d37104
Next: Junio C Hamano
Message 1 of 5 in “Fix memory leak in get_reachable_subset”
  1. Fix memory leak in get_reachable_subsetMike Hommey, Jun 3, 2023
  2. Junio C HamanoJun 3, 2023
  3. René ScharfeJun 3, 2023
  4. Junio C HamanoJun 4, 2023
  5. Derrick StoleeJun 5, 2023

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.