threads / bug / 31290

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

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

## tl;dr

2 messages between Aug 20, 2012 and Aug 20, 2012.

replies: 1people: 2as markdown or json

Jose Nobile· Aug 20, 2012, 05:12 UTC · lore

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?

This is not in accordance with the first paragraph of the homepage of main page of GIT:

Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

Greetings, José Nobile

Robin Rosenberg· Aug 20, 2012, 05:48 UTC · re: Jose Nobile · lore

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

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