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

Re: git gc exit with out of memory, malloc failed error

From
Carlos Martín Nieto <carlos@cmartin.tk>
Date
Sep 15, 2011, 09:16 UTC
Message-ID
<1316078174.2019.15.camel@bee.lab.cmartin.tk>
In-Reply-To
<CA+sFfMdXLkSE_RXB28TSx0JpPVjwe1Rf+03TkiT2YJjYH7m9MQ@mail.gmail.com>
On Wed, 2011-09-14 at 21:29 -0500, Brandon Casey wrote:
Show 15 quoted lines
> [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
Previous: Brandon Casey
Message 5 of 5 in “git gc exit with out of memory, malloc failed error”
  1. Alexander KostikovSep 15, 2011
  2. David Michael BarrSep 15, 2011
  3. Alexander KostikovSep 15, 2011
  4. Brandon CaseySep 15, 2011
  5. Carlos Martín NietoSep 15, 2011

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.