From: "pradeep singh rautela" <rautelap@gmail.com>
To: "Nicolas Pitre" <nico@cam.org>
Cc: git@vger.kernel.org
Subject: Re: git-clone fails with out of memory,malloc failed7
Date: Tue, 12 Feb 2008 23:22:19 +0530 [thread overview]
Message-ID: <6bc632150802120952n2b6abbb4tea8cde0fddbf7a7c@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.1.00.0802121218280.2732@xanadu.home>
[...]
>
> > Better if this is a known issue ?
>
> It is not.
>
> > isn't 1 GB of RAM enough for git???
>
> It is plenty sufficient with the repository you tried it on.
>
> > luser@helvella:/opt/repo/archive$ sudo git-clone
> > git://git.kernel.org/pub/scm/linux/kernel/git/mingo/linux-2.6-kgdb.git
> > [sudo] password for luser:
>
> Why do you use sudo to run git?
because I(as luser :) ) did not have write permissions in the
directory where I intend to clone the repo.
>
> > Initialized empty Git repository in /opt/repo/archive/linux-2.6-kgdb/.git/
> > remote: Counting objects: 712950, done.
> > remote: Compressing objects: 100% (124251/124251), done.
> > remote: Total 712950 (delta 591747), reused 708812 (delta 587713)
> > Receiving objects: 100% (712950/712950), 173.74 MiB | 40 KiB/s, done.
> > fatal: Out of memory, malloc failed7)
> > fatal: index-pack failed
>
> I just cloned the above repository with Git v1.5.4 with no problem at
> all, and index-pack never used more than 52 megs of actual memory.
>
> Puzzled.
me too.Thought it may be some git issue so reported.
Seems like it is once in a blue moon situation.
Nevermind, thanks for reply.
Cu,
--Pradeep
--
Pradeep Singh Rautela
http://eagain.wordpress.com
http://emptydomain.googlepages.com
prev parent reply other threads:[~2008-02-12 17:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 15:57 git-clone fails with out of memory,malloc failed7 pradeep singh rautela
2008-02-12 17:23 ` Nicolas Pitre
2008-02-12 17:52 ` pradeep singh rautela [this message]
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=6bc632150802120952n2b6abbb4tea8cde0fddbf7a7c@mail.gmail.com \
--to=rautelap@gmail.com \
--cc=git@vger.kernel.org \
--cc=nico@cam.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).