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

Re: [PATCH] Allocate msg only after fatal checks to avoid leaks

From
lidongyan <502024330056@smail.nju.edu.cn>
Date
Jun 14, 2025, 08:26 UTC
Message-ID
<3993AF96-E03D-46AB-B18E-8E6C1108EC45@smail.nju.edu.cn>
In-Reply-To
<pull.1998.git.git.1749843142000.gitgitgadget@gmail.com>
Alex via GitGitGadget <gitgitgadget@gmail.com> writes:
Show 6 quoted lines
> 
> From: jinyaoguo <guo846@purdue.edu>
> 
> In parse_reuse_arg, we previously called xmalloc and strbuf_init
> before resolving the ref and reading the object, leading to a
> leaked msg on die() paths. This change moves the allocation of

A memory leak on the die() path shouldn't be considered a real leak, right? Since the OS will clean up all memory once the process terminates, explicitly freeing msg isn't necessary in this case.

Lidong
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 7 in “Allocate msg only after fatal checks to avoid leaks”
  1. Allocate msg only after fatal checks to avoid leaksAlex via GitGitGadget, Jun 13, 2025
  2. Junio C HamanoJun 13, 2025
  3. lidongyanJun 14, 2025
  4. Junio C HamanoJun 14, 2025
  5. lidongyanJun 14, 2025
  6. Jeff KingJun 14, 2025
  7. Junio C HamanoJun 15, 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.