From: Jeff King <peff@peff.net>
To: Andrzej Hunt <andrzej@ahunt.org>
Cc: "우승훈[ 대학원석·박사통합과정수료연구(재학) / 컴퓨터학과 ]" <seunghoonwoo@korea.ac.kr>,
git@vger.kernel.org, hanjiyeon0@gmail.com
Subject: Re: Possible memory leak bug reports for the latest "git" repository.
Date: Fri, 9 Apr 2021 14:46:11 -0400 [thread overview]
Message-ID: <YHCg8ycLahSwNvJL@coredump.intra.peff.net> (raw)
In-Reply-To: <b96f76f2-db00-cc7c-eb83-3033873023ec@ahunt.org>
On Fri, Apr 09, 2021 at 06:49:39PM +0200, Andrzej Hunt wrote:
> > ==63105== 40 bytes in 1 blocks are possibly lost in loss record 38 of 142
> > ==63105== at 0x4C31B0F: malloc (in
> > /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
> > ==63105== by 0x34013A: do_xmalloc (wrapper.c:41)
> > ==63105== by 0x355BB5: chdir_notify_register (chdir-notify.c:18)
> [...]
>
> These are a bit odd: chdir_notify_register() is attaching the newly
> allocated memory to a static list (chdir_notify_entries), and I can't see
> any obvious reason why this would leak (but maybe valgrind doesn't like
> static pointers)? Either way, this doesn't seem to be anywhere near the
> regex code.
These "possibly lost" are false positives; there's more discussion in
this thread:
https://lore.kernel.org/git/20201117002435.GA13516@coredump.intra.peff.net/
-Peff
prev parent reply other threads:[~2021-04-09 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 13:59 Possible memory leak bug reports for the latest "git" repository 우승훈[ 대학원석·박사통합과정수료연구(재학) / 컴퓨터학과 ]
2021-04-09 16:49 ` Andrzej Hunt
2021-04-09 18:46 ` Jeff King [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YHCg8ycLahSwNvJL@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=andrzej@ahunt.org \
--cc=git@vger.kernel.org \
--cc=hanjiyeon0@gmail.com \
--cc=seunghoonwoo@korea.ac.kr \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).