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

all memory consuming `git diff-tree` bug

From
DHDale Henrichs <dale.henrichs@gemtalksystems.com>
Date
Apr 28, 2020, 00:28 UTC
Message-ID
<5e00fe77-3f72-0729-2b30-9f4f98a28b1c@gemtalksystems.com>

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: Jeff King
Message 1 of 3 in “all memory consuming `git diff-tree` bug”
  1. Dale HenrichsApr 28, 2020
  2. Jeff KingApr 28, 2020
  3. Antoine PelisseApr 28, 2020

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.