threads / discuss / 12058

git-clone fails with out of memory,malloc failed7

Subject: git-clone fails with out of memory,malloc failed7

## tl;dr

3 messages between Feb 12, 2008 and Feb 12, 2008.

replies: 2people: 2as markdown or json

pradeep singh rautela· Feb 12, 2008, 15:57 UTC · lore

Hi All,

I compiled a fresh git 1.5.4 and tried to clone Ingo's kgdb-lite tree. I got rather strange out of memory. malloc failed7 error.

I am using a 32 bit kernel on a pentium D processor with 1 GB of ram.

Is this a git issue or something else? Can someone help me in telling me which is the correct place to report this? Better if this is a known issue ?

isn't 1 GB of RAM enough for git???

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: 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 fetch-pack from 'git://git.kernel.org/pub/scm/linux/kernel/git/mingo/linux-2.6-kgdb.git' failed.

ps: Please CC me, as I am not subscribed to the list.

Thanks,
           --Pradeep

-- 
Pradeep Singh Rautela
http://eagain.wordpress.com
http://emptydomain.googlepages.com

Nicolas Pitre· Feb 12, 2008, 17:23 UTC · re: pradeep singh rautela · lore

Re: git-clone fails with out of memory,malloc failed7

On Tue, 12 Feb 2008, pradeep singh rautela wrote:

Show 9 quoted lines

> Hi All,
> 
> I compiled a fresh git 1.5.4 and tried to clone Ingo's kgdb-lite tree.
> I got rather strange out of memory. malloc failed7 error.
> 
> I am using a 32 bit kernel on a pentium D processor with 1 GB of ram.
> 
> Is this a git issue or something else?
> Can someone help me in telling me which is the correct place to report this?

This is the right place.

> 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?

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

Nicolas

pradeep singh rautela· Feb 12, 2008, 17:52 UTC · re: Nicolas Pitre · lore

Re: git-clone fails with out of memory,malloc failed7

[...]

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