From: Dale Henrichs <dale.henrichs@gemtalksystems.com>
To: git@vger.kernel.org
Cc: Kurt Kilpela <kurt.kilpela@gemtalksystems.com>
Subject: all memory consuming `git diff-tree` bug
Date: Mon, 27 Apr 2020 17:28:26 -0700 [thread overview]
Message-ID: <5e00fe77-3f72-0729-2b30-9f4f98a28b1c@gemtalksystems.com> (raw)
When I execute the follow set of commands, the `git diff-tree` command
will go on to consume all 30G of ram and then 30G of swap on a system
running Ubuntu 18.04.
git clone git@github.com:GemTalk/Rowan.git
cd Rowan
git checkout c70f69b50dc90c0a6207a5aa36705b71b59b92b3
git diff-tree -r -p --textconv --submodule -C --cc --no-commit-id -U3
--root c70f69b50dc90c0a6207a5aa36705b71b59b92b3
I'm running git 2.26.2 (built from source). The git command line was
generated by gitk. It originally showed up in 2.17.1, but reproduced in
the latest version of git.
Clicking nearby commits (ccffec29f977f9324e8120bf550c745189e76f70 and
8b08cec96bbb74b54046abbdb49a5bbd2f82fc3b finish almost immediately, so
there seems to be something special about that particular commit.
Dale
next reply other threads:[~2020-04-28 0:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 0:28 Dale Henrichs [this message]
2020-04-28 4:10 ` all memory consuming `git diff-tree` bug Jeff King
2020-04-28 4:18 ` Antoine Pelisse
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=5e00fe77-3f72-0729-2b30-9f4f98a28b1c@gemtalksystems.com \
--to=dale.henrichs@gemtalksystems.com \
--cc=git@vger.kernel.org \
--cc=kurt.kilpela@gemtalksystems.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