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

Re: [PATCH] Fix memory leak in get_reachable_subset

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 3, 2023, 02:02 UTC
Message-ID
<xmqqedmt7167.fsf@gitster.g>
In-Reply-To
<20230603002819.1122129-1-mh@glandium.org>
Mike Hommey <mh@glandium.org> writes:
> Signed-off-by: Mike Hommey <mh@glandium.org>
> ---

As most lines in the affected function seems to come from your fcb2c076 (commit-reach: implement get_reachable_subset, 2018-11-02), I'll redirect the review of this patch to you.

Thanks.
Show 15 quoted lines
>  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);
Previous: Mike HommeyNext: René Scharfe
Message 2 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.