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

[FYI] very large text files and their problems.

From
IKIan Kumlien <pomac@vapor.com>
Date
Feb 22, 2012, 15:49 UTC
Message-ID
<20120222154926.GC11202@pomac.netswarm.net>
Hi,

We just saw a interesting issue, git compressed a ~3.4 gb project to ~57 mb. But when we tried to clone it on a big machine we got:

fatal: Out of memory, malloc failed (tried to allocate 18446744072724798634 bytes)

This is already fixed in the 1.7.10 mainline - but it also seems like git needs to have atleast the same ammount of memory as the largest file free... Couldn't this be worked around?

On a (32 bit) machine with 4GB memory - results in: fatal: Out of memory, malloc failed (tried to allocate 3310214313 bytes)

(and i see how this could be a problem, but couldn't it be mitigated? or is it bydesign and intended behaviour?)

I'm not subscribed to please keep me in CC.
/Ian Kumlien
Next: Nguyen Thai Ngoc Duy
Message 1 of 5 in “[FYI] very large text files and their problems.”
  1. Ian KumlienFeb 22, 2012
  2. Nguyen Thai Ngoc DuyFeb 22, 2012
  3. Ian KumlienFeb 24, 2012
  4. Nguyen Thai Ngoc DuyFeb 24, 2012
  5. Ian KumlienFeb 24, 2012

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.