On Fri, Jan 11, 2008 at 10:18:32PM +0000, Charles Bailey wrote:
I have seen this exact type of failure (commit reports possible oom, but
commit appears to have succeeded) with most recent gits.
This is almost certainly caused not by the commit action itself (which
uses very little memory) but by the resulting diffstat to show what
happened. So the commit has already been "committed" to disk by the time
it crashes.
This is at least the case with Brandon's problem (his stack trace shows
the diff happening).
-Peff