From: Pau Garcia i Quiles <pgquiles@elpauer.org>
To: Jeff King <peff@peff.net>
Cc: David Abrahams <dave@boostpro.com>, git@vger.kernel.org
Subject: Re: "malloc failed"
Date: Wed, 28 Jan 2009 23:16:32 +0100 [thread overview]
Message-ID: <3af572ac0901281416x5adef0eak89bd4b40fda52c2b@mail.gmail.com> (raw)
In-Reply-To: <20090128050225.GA18546@coredump.intra.peff.net>
On Wed, Jan 28, 2009 at 6:02 AM, Jeff King <peff@peff.net> wrote:
> How big is the repository? How big are the biggest files? I have a
> 3.5G repo with files ranging from a few bytes to about 180M. I've never
> run into malloc problems or gone into swap on my measly 1G box.
> How does your dataset compare?
I also have malloc problems but only on Windows, on Linux it works fine.
My case: I have a 500 MB repository with a 1GB working tree, with
binary files ranging from 100KB to 50MB and a few thousand source
files.
I have two branches ('master' and 'cmake') and the latter has suffered
a huge hierarchy reorganization.
When I merge 'master' in 'cmake', if I use the 'subtree' strategy, it
works fine. If I use any other strategy, after a couple of minutes I
receive a "malloc failed" and the tree is all messed up. As I said, on
Linux it works fine, so maybe it's a Windows-specific problem.
--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)
next prev parent reply other threads:[~2009-01-28 22:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 15:04 "malloc failed" David Abrahams
2009-01-27 15:29 ` Shawn O. Pearce
2009-01-27 15:32 ` David Abrahams
2009-01-27 18:02 ` Johannes Schindelin
2009-01-28 5:02 ` Jeff King
2009-01-28 21:53 ` David Abrahams
2009-01-29 0:06 ` David Abrahams
2009-01-29 5:20 ` Jeff King
2009-01-29 5:56 ` Jeff King
2009-01-29 7:53 ` Junio C Hamano
2009-01-29 13:10 ` David Abrahams
2009-01-29 13:41 ` Andreas Ericsson
2009-01-30 4:49 ` Jeff King
2009-01-28 22:16 ` Pau Garcia i Quiles [this message]
2009-01-29 5:14 ` Jeff King
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=3af572ac0901281416x5adef0eak89bd4b40fda52c2b@mail.gmail.com \
--to=pgquiles@elpauer.org \
--cc=dave@boostpro.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).