Re: fatal: Out of memory, malloc failed

From: Alex Riesen <raa.lkml@gmail.com>
Date: Apr 16, 2007, 09:21 UTC
Message-ID: <81b0412b0704160221o269fbd6al133a44148c75e38a@mail.gmail.com>
In-Reply-To: <46232FAC.4080506@eircom.net>

On 4/16/07, Alan Larkin <nobrow@eircom.net> wrote:

Show 19 quoted lines

> >> > 72Mb is nothing. Is it Windows/cygwin, by any chance? (I see the
> >> > problem there sometimes. Tried debugging it, got into some ugly
> >> > cygwin-windows interactions, threw up, did the same you did and tried
> >> > to forget it all).
> >>
> >> Thats what I thought, but malloc continued to fail until the 72Mb file
> >> was removed.
> >>
> >> No, my server is running Debian. I had the push problem when logged in
> >> on that.
> >> It worked when I pushed it from a Gentoo box.
> >
> > Ok, now _that_ is interesting... Any limits on that server?
> > What git version?  There were some memory leaks fixed recently...
>
> Ah, perhaps youre on to something there. The version Im running on the server is
> 1.4.4.4 (from apt package manager), but on my own machine (from whence the push
> was successful) its 1.5.0.5. Still, youd expect the problem to have effected more
> people if its a leak or something in the older version.

That's how the leaks were found: people were affected and complained :) But it also a bit of unusual repo you have: not many have objects more the 10Mb in their sources. Anyway, give the new version a try. Maybe it was fixed, or maybe we have a chance to improve the current version.