# git-svn -- out of memory

2 messages from 2009-02-14 to 2009-02-16. Participants: Alfred M. Szmidt, Eric Wong.
Thread: https://gitlist.dev/t/17788

## Alfred M. Szmidt, 2009-02-14 10:40

Subject: git-svn -- out of memory
Message-ID: <1234608003.115771.3468.nullmailer@beryx.hq.kred>
URL: https://gitlist.dev/e/1234608003.115771.3468.nullmailer%40beryx.hq.kred

```
Hi,

when doing a `git svn clone' on a subversion repository that contains
a large file (>1GiB), `git svn' dies with the following:

ams@trillian:~$ git svn clone REPO -T trunk -b branches -t tags
[...]
fatal: Out of memory? mmap failed: Cannot allocate memory
hash-object -w --stdin-paths: command returned error: 128

error closing pipe: Bad file descriptor at /usr/local/bin/libexec/git-core//git-svn line 0
error closing pipe: Bad file descriptor at /usr/local/bin/libexec/git-core//git-svn line 0

Doing a `git repack' doesn't help either.  Anyone got a clue how to
either solve, or work around this?

git version 1.6.1.3

Cheers.

```

## Eric Wong, 2009-02-16 00:38

Subject: Re: git-svn -- out of memory
Message-ID: <20090216003835.GA5687@untitled>
URL: https://gitlist.dev/e/20090216003835.GA5687%40untitled
In-Reply-To: <1234608003.115771.3468.nullmailer@beryx.hq.kred>

```
"Alfred M. Szmidt" <ams@gnu.org> wrote:
> Hi,
> 
> when doing a `git svn clone' on a subversion repository that contains
> a large file (>1GiB), `git svn' dies with the following:
> 
> ams@trillian:~$ git svn clone REPO -T trunk -b branches -t tags
> [...]
> fatal: Out of memory? mmap failed: Cannot allocate memory
> hash-object -w --stdin-paths: command returned error: 128
> 
> error closing pipe: Bad file descriptor at /usr/local/bin/libexec/git-core//git-svn line 0
> error closing pipe: Bad file descriptor at /usr/local/bin/libexec/git-core//git-svn line 0
> 
> Doing a `git repack' doesn't help either.  Anyone got a clue how to
> either solve, or work around this?
> 
> git version 1.6.1.3

Hi Alfred,

Core git requires objects to be able to fit into (virtual) memory.
Adding more swap space should solve the problem for you, but this is not
only a git-svn problem.

Fwiw, git-svn itself has always had a pretty strict "no slurping"
policy.

-- 
Eric Wong

```