From: Ian Kumlien <pomac@vapor.com>
Date: Wed, 22 Feb 2012 15:49:26 GMT
Subject: [FYI] very large text files and their problems.
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