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

Re: BUG Report. Why GIT commit need 30GB of memory for a commit?

From
Robin Rosenberg <robin.rosenberg@dewire.com>
Date
Aug 20, 2012, 05:48 UTC
Message-ID
<5031CFBF.903@dewire.com>
In-Reply-To
<CAJ69RUQ++RpfgDmPh2k6n1e61xX9OZ_tvG5K7Q4CXvh7i2cj6w@mail.gmail.com>
Jose Nobile skrev 2012-08-20 07.12:
Show 12 quoted lines
> I have a big repository, around 80GB
> git --version
> #git version 1.7.12
> git init .
> #Initialized empty Git repository in /reponame/.git/
> git add -A .
>
> git commmit -m "Backup 2012-08-19 03:43:44"
> #fatal: Out of memory, malloc failed (tried to allocate 32220431361 bytes)
> #[master (root-commit) 8053f0d] Backup 2012-08-19 03:43:44
>
>   Why GIT need 30GB of memory for a commit?
It may be trying to compute a commit summary. Add -q to avoid the work.
-- robin
Previous: Jose Nobile
Message 2 of 2 in “BUG Report. Why GIT commit need 30GB of memory for a commit?”
  1. Jose NobileAug 20, 2012
  2. Robin RosenbergAug 20, 2012

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.