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

Re: [PATCH] revision: fix memory leak in prepare_show_merge()

From
lidongyan <502024330056@smail.nju.edu.cn>
Date
Jun 6, 2025, 07:31 UTC
Message-ID
<90FE268F-2309-49F0-9C3B-DFB207CE6F47@smail.nju.edu.cn>
In-Reply-To
<xmqqmsal7vqx.fsf@gitster.g>
2025年6月6日 04:56,Junio C Hamano <gitster@pobox.com> 写道:
Show 45 quoted lines
> 
> Patrick Steinhardt <ps@pks.im> writes:
> 
>> On Wed, Jun 04, 2025 at 03:08:56AM +0000, Lidong Yan via GitGitGadget wrote:
>>> From: Lidong Yan <502024330056@smail.nju.edu.cn>
>>> 
>>> In revision.c:prepare_show_merge(), we allocated an array in prune
>>> but forget to free it. Since parse_pathspec is not responsible to
>>> free prune, we should add `free(prune)` in the end of prepare_show_merge().
>> 
>> That is a rather obvious memory leak indeed. Do you know why we never
>> detected the leak in our CI? Is this code path not exercised at all by
>> our tests?
> 
> I think we have no "show --merge" test.  Something like this may be
> minimally sufficient.
> 
> t/t7007-show.sh | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
> 
> diff --git c/t/t7007-show.sh w/t/t7007-show.sh
> index d6cc69e0f2..99f4d0b963 100755
> --- c/t/t7007-show.sh
> +++ w/t/t7007-show.sh
> @@ -167,4 +167,19 @@ test_expect_success 'show --graph is forbidden' '
>   test_must_fail git show --graph HEAD
> '
> 
> +test_expect_success 'unmerged index' '
> + git reset --hard &&
> + git commit --allow-empty -m initial &&
> + git rev-parse HEAD >.git/MERGE_HEAD &&
> + blob1=$(echo hello | git hash-object -w --stdin) &&
> + blob2=$(echo goodbye | git hash-object -w --stdin) &&
> + blob3=$(echo world | git hash-object -w --stdin) &&
> + git update-index --add --index-info <<-EOF &&
> + 100644 $blob1 1 conflicting
> + 100644 $blob2 2 conflicting
> + 100755 $blob3 3 conflicting
> + EOF
> + git show --merge HEAD
> +'
> +
> test_done
> 
I could add this test case into my patch. Though I don’t understand
> + git rev-parse HEAD >.git/MERGE_HEAD &&

If HEAD is equal to MERGE_HEAD. Would git show —merge still works as usual? How about something like this

diff --git a/t/t7007-show.sh b/t/t7007-show.sh
index d6cc69e0f2..f693b6e24b 100755
--- a/t/t7007-show.sh
+++ b/t/t7007-show.sh
@@ -167,4 +167,28 @@ test_expect_success 'show --graph is forbidden' '
   test_must_fail git show --graph HEAD
 '
 
+test_expect_success 'unmerged index' '
+       git reset --hard &&
+
+       git switch -C base &&
+       echo "base" > conflicting &&
+       git add conflicting &&
+       git commit -m "base" &&
+
+       git branch hello &&
+       git branch goodbye &&
+
+       git switch hello &&
+       echo "hello" > conflicting &&
+       git commit -am "hello" &&
+
+       git switch goodbye &&
+       echo "goodbye" > conflicting &&
+       git commit -am "goodbye" &&
+
+       git switch hello &&
+       test_must_fail git merge goodbye &&
+       git show --merge HEAD
+'
+
 test_done
Previous: Junio C HamanoNext: Junio C Hamano
Message 7 of 12 in “revision: fix memory leak in prepare_show_merge()”
  1. revision: fix memory leak in prepare_show_merge()Lidong Yan via GitGitGadget, Jun 4, 2025
  2. Patrick SteinhardtJun 4, 2025
  3. lidongyanJun 4, 2025
  4. Patrick SteinhardtJun 4, 2025
  5. lidongyanJun 4, 2025
  6. Junio C HamanoJun 5, 2025
  7. lidongyanJun 6, 2025
  8. Junio C HamanoJun 6, 2025
  9. lidongyanJun 9, 2025
  10. revision: fix memory leak in prepare_show_merge()Lidong Yan via GitGitGadget, Jun 9, 2025
  11. Junio C HamanoJun 9, 2025
  12. revision: fix memory leak in prepare_show_merge()Lidong Yan via GitGitGadget, Jun 10, 2025

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.