Re: git tag triggers out-of-memory killer
From: Olaf Hering <hidden>
Date: 2022-07-12 10:22:43
Mon, 11 Jul 2022 10:06:32 -0400 Jeff King [off-list ref]:
quoted hunk ↗ jump to hunk
--- 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
Attachments
- (unnamed) [application/pgp-signature] 833 bytes