git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brandon Williams <bmwill@google.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] grep: plug a trivial memory leak
Date: Mon, 10 Apr 2017 10:17:19 -0700	[thread overview]
Message-ID: <20170410171719.GB113751@google.com> (raw)
In-Reply-To: <20170409195900.32701-1-avarab@gmail.com>

On 04/09, Ævar Arnfjörð Bjarmason wrote:
> Change the cleanup phase for the grep command to free the pathspec
> struct that's allocated earlier in the same block, and used just a few
> lines earlier.
> 
> With "grep hi README.md" valgrind reports a loss of 239 bytes now,
> down from 351.
> 
> The relevant --num-callers=40 --leak-check=full --show-leak-kinds=all
> backtrace is:
> 
>     [...] 187 (112 direct, 75 indirect) bytes in 1 blocks are definitely lost in loss record 70 of 110
>     [...]    at 0x4C2BBAF: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
>     [...]    by 0x60B339: do_xmalloc (wrapper.c:59)
>     [...]    by 0x60B2F6: xmalloc (wrapper.c:86)
>     [...]    by 0x576B37: parse_pathspec (pathspec.c:652)
>     [...]    by 0x4519F0: cmd_grep (grep.c:1215)
>     [...]    by 0x4062EF: run_builtin (git.c:371)
>     [...]    by 0x40544D: handle_builtin (git.c:572)
>     [...]    by 0x4060A2: run_argv (git.c:624)
>     [...]    by 0x4051C6: cmd_main (git.c:701)
>     [...]    by 0x4C5901: main (common-main.c:43)
> 
> Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
> ---
> 
> Since pretty much any non-trivial git command leaks because it skips
> cleanup are patches in this category even accepted? Worth a try...

Some may argue that the program will terminate soon and that the leak is
bounded etc., but I think that plugging leaks is a good thing.  As such,
I like this patch :)

> 
>  builtin/grep.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/builtin/grep.c b/builtin/grep.c
> index 65070c52fc..3ffb5b4e81 100644
> --- a/builtin/grep.c
> +++ b/builtin/grep.c
> @@ -1299,6 +1299,7 @@ int cmd_grep(int argc, const char **argv, const char *prefix)
>  		hit |= wait_all();
>  	if (hit && show_in_pager)
>  		run_pager(&opt, prefix);
> +	clear_pathspec(&pathspec);
>  	free_grep_patterns(&opt);
>  	return !hit;
>  }
> -- 
> 2.11.0
> 

-- 
Brandon Williams

      reply	other threads:[~2017-04-10 17:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-09 19:59 [PATCH] grep: plug a trivial memory leak Ævar Arnfjörð Bjarmason
2017-04-10 17:17 ` Brandon Williams [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170410171719.GB113751@google.com \
    --to=bmwill@google.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).