From: "Carlos Martín Nieto" <carlos@cmartin.tk>
To: Brandon Casey <drafnel@gmail.com>
Cc: git@vger.kernel.org, Alexander Kostikov <alex.kostikov@gmail.com>
Subject: Re: git gc exit with out of memory, malloc failed error
Date: Thu, 15 Sep 2011 11:16:13 +0200 [thread overview]
Message-ID: <1316078174.2019.15.camel@bee.lab.cmartin.tk> (raw)
In-Reply-To: <CA+sFfMdXLkSE_RXB28TSx0JpPVjwe1Rf+03TkiT2YJjYH7m9MQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 994 bytes --]
On Wed, 2011-09-14 at 21:29 -0500, Brandon Casey wrote:
> [resend since gmail's Rich formatting was enabled]
>
> On Wed, Sep 14, 2011 at 8:33 PM, Alexander Kostikov
> <alex.kostikov@gmail.com> wrote:
> >
> > I'm new to git and I'm getting the following out of memory error on git gc:
> >
> > $ git gc
> > Counting objects: 80818, done.
> > Delta compression using up to 8 threads.
> > fatal: Out of memory, malloc failed (tried to allocate 24359675 bytes)
> > error: failed to run repack
>
> Try reducing the number of threads that are used. You must have some
> pretty large objects if you have 24GB and ran out of memory. The
IIRC the 32-bit Windows builds limit each user process to 2GB. If
msysgit is built in 32-bit mode, it's possible (probable even, in order
to remain backwards-compatible) that it's hitting this limit, rather
than the physical limit of the machine. If it's using 8 threads, it
means that there are 256MB available for each thread.
cmn
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
prev parent reply other threads:[~2011-09-15 9:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 1:33 git gc exit with out of memory, malloc failed error Alexander Kostikov
2011-09-15 2:20 ` David Michael Barr
2011-09-15 2:42 ` Alexander Kostikov
[not found] ` <CA+sFfMcfy=GCFrCjonQXvXRQu=hLjDvQViJJ75xqa72Gb23MgQ@mail.gmail.com>
2011-09-15 2:29 ` Brandon Casey
2011-09-15 9:16 ` Carlos Martín Nieto [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=1316078174.2019.15.camel@bee.lab.cmartin.tk \
--to=carlos@cmartin.tk \
--cc=alex.kostikov@gmail.com \
--cc=drafnel@gmail.com \
--cc=git@vger.kernel.org \
/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).