Re: Git chokes on large file

From: Dale R. Worley <worley@alum.mit.edu>
Date: May 28, 2014, 18:15 UTC
Message-ID: <201405281815.s4SIF5hF025886@hobgoblin.ariadne.com>
In-Reply-To: <CACsJy8BM1f1pJPzGPf--a-kUim6wyX+Mr1AfMupY3mpREY+8DA@mail.gmail.com>

> From: Duy Nguyen <pclouds@gmail.com>

Show 6 quoted lines

> I don't know how many commands are hit by this. If you have time and
> gdb, please put a break point in die_builtin() function and send
> backtraces for those that fail. You could speed up the process by
> creating a smaller file and set the environment variable
> GIT_ALLOC_LIMIT (in kilobytes) to a number lower than that size. If
> git attempts to allocate a block larger than that limit it'll die.

I don't use Git enough to exercise it well. And there are dozens of commands with hundreds of options.

As someone else has noted, if I run 'git commit -q --no-status', it doesn't crash.

It seems that much of Git was coded under the assumption that any file could always be held entirely in RAM. Who made that mistake? Are people so out of touch with reality?

Dale