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

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

From
Patrick Steinhardt <ps@pks.im>
Date
Jun 4, 2025, 07:48 UTC
Message-ID
<aD_6T0lUOsqrb5sH@pks.im>
In-Reply-To
<pull.1989.git.git.1749006537271.gitgitgadget@gmail.com>
On Wed, Jun 04, 2025 at 03:08:56AM +0000, Lidong Yan via GitGitGadget wrote:
Show 5 quoted lines
> 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?

Patrick
Previous: Lidong Yan via GitGitGadgetNext: lidongyan
Message 2 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.