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

how to keep git-fetch from running out of memory?

From
Kartik Agaram <ak@akkartik.com>
Date
May 15, 2011, 05:24 UTC
Message-ID
<BANLkTinnOTr+PUzBMpx1DLcxs8CVWjy33A@mail.gmail.com>

I have a git repo with some large files that I'm no longer able to update. git fetch keeps running out of memory:

  fatal: Out of memory, malloc failed
  fatal: unpack-objects died with error code 128

Anybody know how to keep it from compressing the refs into packfiles? I've experimented with core.compression, pack.compression, pack.windowMemory, pack.packSizeLimit, all without luck :(

Next: Shawn Pearce
Message 1 of 4 in “how to keep git-fetch from running out of memory?”
  1. Kartik AgaramMay 15, 2011
  2. Shawn PearceMay 15, 2011
  3. Junio C HamanoMay 15, 2011
  4. Shawn PearceMay 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.