Re: git tag triggers out-of-memory killer

From: Olaf Hering <olaf@aepfle.de>
Date: Jul 12, 2022, 10:22 UTC
Message-ID: <20220712122226.183fff9b.olaf@aepfle.de>
In-Reply-To: <YswuaPx6Mk7YkIim@coredump.intra.peff.net>

Mon, 11 Jul 2022 10:06:32 -0400 Jeff King <peff@peff.net>:

Show 12 quoted lines

> --- a/builtin/tag.c
> +++ b/builtin/tag.c
> @@ -486,6 +486,8 @@ int cmd_tag(int argc, const char **argv, const char *prefix)
>  	int ret = 0;
>  	const char *only_in_list = NULL;
>  
> +	save_commit_buffer = 0;
> +
>  	setup_ref_filter_porcelain_msg();
>  
>  	git_config(git_tag_config, &sorting_options);
>

Thanks, this patch helps.

The individual git processes start with a maximum of ~320M, and slowly reach around ~600M as maximum.

I was not aware of commit-graph. After writing a commit-graph the processing is much faster, and an unmodified git 2.35.3 uses ~320M as a maximum.

Olaf