git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Riesen <raa.lkml@gmail.com>
To: Alan Larkin <nobrow@eircom.net>
Cc: git@vger.kernel.org, Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: fatal: Out of memory, malloc failed
Date: Sun, 15 Apr 2007 23:40:50 +0200	[thread overview]
Message-ID: <20070415214050.GA4417@steel.home> (raw)
In-Reply-To: <462277CD.5020609@eircom.net>

Alan Larkin, Sun, Apr 15, 2007 21:06:53 +0200:
> >> Its not a huge push Im trying to do here (<about 150Mb) but
> >> always malloc fails!
> > 
> > Any huge objects?
> > 
> 
> There were a couple of big files. I removed a 72Mb one (making 47Mb
> the biggest one left in the project) and made the push and it
> worked. I later pulled the project down to a different machine,
> added the 72Mb file back in, and pushed to the server and it worked.
> So apparently it's a platform specific problem. If anybody's
> particularly interested I could replicate it under gdb and pass on
> any info, but if not I wont ... job's done, Im happy.

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).

  reply	other threads:[~2007-04-15 21:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-13 17:25 fatal: Out of memory, malloc failed Alan Larkin
2007-04-13 18:53 ` Linus Torvalds
2007-04-15 19:06   ` Alan Larkin
2007-04-15 21:40     ` Alex Riesen [this message]
2007-04-16  7:46       ` Alan Larkin
2007-04-16  7:54         ` Julian Phillips
2007-04-16  8:02           ` Alan Larkin
2007-04-16  8:03           ` Alex Riesen
2007-04-16  8:00         ` Alex Riesen
2007-04-16  8:11           ` Alan Larkin
2007-04-16  9:21             ` Alex Riesen

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=20070415214050.GA4417@steel.home \
    --to=raa.lkml@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=nobrow@eircom.net \
    --cc=torvalds@linux-foundation.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).