From: Ian Kumlien <pomac@vapor.com>
To: git@vger.kernel.org
Subject: [FYI] very large text files and their problems.
Date: Wed, 22 Feb 2012 16:49:26 +0100 [thread overview]
Message-ID: <20120222154926.GC11202@pomac.netswarm.net> (raw)
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 reply other threads:[~2012-02-22 15:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 15:49 Ian Kumlien [this message]
2012-02-22 16:18 ` [FYI] very large text files and their problems Nguyen Thai Ngoc Duy
2012-02-24 10:11 ` Ian Kumlien
2012-02-24 11:14 ` Nguyen Thai Ngoc Duy
2012-02-24 12:55 ` Ian Kumlien
-- strict thread matches above, loose matches on Subject: below --
2012-02-22 18:39 Ian Kumlien
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=20120222154926.GC11202@pomac.netswarm.net \
--to=pomac@vapor.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).