Re: git-clone fails with out of memory,malloc failed7
- From
- pradeep singh rautela <rautelap@gmail.com>
- Date
- Feb 12, 2008, 17:52 UTC
- Message-ID
- <6bc632150802120952n2b6abbb4tea8cde0fddbf7a7c@mail.gmail.com>
- In-Reply-To
- <alpine.LFD.1.00.0802121218280.2732@xanadu.home>
[...]
Show 14 quoted lines
> > > 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.
Show 13 quoted lines
> > > 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