From: Stephen Boyd <sboyd@codeaurora.org>
To: git@vger.kernel.org
Subject: git rev-list | git cherry-pick --stdin is leaky
Date: Mon, 29 Apr 2013 17:11:04 -0700 [thread overview]
Message-ID: <517F0C18.8060703@codeaurora.org> (raw)
(resending since the attachment seems to make vger sad)
Hi,
I'm running git rev-list | git cherry-pick --stdin on a range of about
300 commits. Eventually the chery-pick dies with:
error: cannot fork() for commit: Cannot allocate memory
Running valgrind shows me that the tree traversal code is leaking
gigabytes of memory (particularly unpack_callback). Since cherry-pick is
a very long running process all these allocations are never freed and
eventually I run out of memory. The worst offender and summary is:
==7986== 938,956,692 (929,961,582 direct, 8,995,110 indirect) bytes in
7,765,439 blocks are definitely lost in loss record 257 of 257
==7986== at 0x4C267CC: calloc (vg_replace_malloc.c:467)
==7986== by 0x4FAF57: xcalloc (wrapper.c:119)
==7986== by 0x4F5281: unpack_callback (unpack-trees.c:539)
==7986== by 0x4F40E5: traverse_trees (tree-walk.c:407)
==7986== by 0x4F586C: unpack_callback (unpack-trees.c:467)
==7986== by 0x4F40E5: traverse_trees (tree-walk.c:407)
==7986== by 0x4F586C: unpack_callback (unpack-trees.c:467)
==7986== by 0x4F40E5: traverse_trees (tree-walk.c:407)
==7986== by 0x4F586C: unpack_callback (unpack-trees.c:467)
==7986== by 0x4F40E5: traverse_trees (tree-walk.c:407)
==7986== by 0x4F586C: unpack_callback (unpack-trees.c:467)
==7986== by 0x4F40E5: traverse_trees (tree-walk.c:407)
==7986==
==7986== LEAK SUMMARY:
==7986== definitely lost: 2,514,117,692 bytes in 21,210,861 blocks
==7986== indirectly lost: 885,481,947 bytes in 10,165,801 blocks
==7986== possibly lost: 650,712,395 bytes in 6,014,309 blocks
==7986== still reachable: 7,734,870 bytes in 47,794 blocks
==7986== suppressed: 0 bytes in 0 blocks
This is against recent git.git
(89740333e8d398f1da701e9023675321bbb9a85b). A workaround is to limit the
amount of commits per cherry-pick invocation, but can we somehow fix the
leaks?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next reply other threads:[~2013-04-30 0:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 0:11 Stephen Boyd [this message]
2013-04-30 18:31 ` git rev-list | git cherry-pick --stdin is leaky Junio C Hamano
2013-04-30 22:47 ` René Scharfe
2013-05-01 18:27 ` Stephen Boyd
2013-05-06 20:16 ` Stephen Boyd
2013-05-09 15:10 ` René Scharfe
2013-05-09 17:24 ` Stephen Boyd
-- strict thread matches above, loose matches on Subject: below --
2013-04-29 23:30 Stephen Boyd
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=517F0C18.8060703@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=git@vger.kernel.org \
/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).