From: Robin Rosenberg <robin.rosenberg@dewire.com>
To: Jose Nobile <jose.nobile@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: BUG Report. Why GIT commit need 30GB of memory for a commit?
Date: Mon, 20 Aug 2012 07:48:47 +0200 [thread overview]
Message-ID: <5031CFBF.903@dewire.com> (raw)
In-Reply-To: <CAJ69RUQ++RpfgDmPh2k6n1e61xX9OZ_tvG5K7Q4CXvh7i2cj6w@mail.gmail.com>
Jose Nobile skrev 2012-08-20 07.12:
> 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
prev parent reply other threads:[~2012-08-20 5:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 5:12 BUG Report. Why GIT commit need 30GB of memory for a commit? Jose Nobile
2012-08-20 5:48 ` Robin Rosenberg [this message]
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=5031CFBF.903@dewire.com \
--to=robin.rosenberg@dewire.com \
--cc=git@vger.kernel.org \
--cc=jose.nobile@gmail.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;
as well as URLs for NNTP newsgroup(s).