Issue #7152 resolved

fatal: Out of memory, malloc failed

Frankie Hayward
created an issue

I've been converting some existing websites into repos for ease of management but seem to be hitting a road block on a few sites. Here is the error message I'm receiving:

Counting objects: 24695, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (22512/22512), done.
fatal: Out of memory, malloc failed
error: pack-objects died with strange error

Specs: Rackspace Cloud Server CentOS6 puppet nginx git

Comments (9)

  1. Nicolas Venegas

    Hi

    Are you seeing this error when pushing to bitbucket.org?

    I feel like maybe you've created this issue in the wrong issue tracker; this is the one for the bitbucket.org website.

    Cheers

    Nicolas

  2. Frankie Hayward reporter

    Hi Nicolas,

    Yes, I'm seeing this error when pushing to a bitbucket.org repo

    Where should I create an issue tracker for this type of situation?

    Thanks,

    Frankie

  3. Nicolas Venegas
    • changed status to open

    Hi

    Sorry, I intuited that you weren't seeing this when pushing to Bitbucket — my bad.

    Reporting it here is fine; you can also get help by emailing support@bitbucket.org.

    What particular repository do you see this problem on? Also, are you trying to push a lots of commits/large commits?

    Cheers

    Nicolas

  4. Frankie Hayward reporter
    • changed status to open

    Hi

    It's a private repo "catalystsquared/yourpatiofurniture.com.git" which I'm pushing a single commit of my entire public directory (a magento + wordpress website)

    Here is an rsync of the same directory:

    sent 983065 bytes  received 3121947609 bytes  5024828.12 bytes/sec
    total size is 4717527304  speedup is 1.51
    

    I looked into this solution but I'm not using Ubuntu http://www.garron.me/bits/create-add-swap-file-ubuntu.html

    Any idea how to get this repo pushed error free?

    Thanks

    Frankie

  5. Erik van Zijst staff

    Wait, is that 5 GB you are trying to push there? If so then that's a really bad idea and a recipe for memory problems, either on our end or even your own workstation.

    Before pushing again, please reorganize that repo. You might have a ton of binary files in there that are really better kept elsewhere that is not a git repo.

    Try to get your repo under a GB (although even that might still give you problems).

  6. Frankie Hayward reporter

    Thanks Erik,

    I understand that I need to push existing projects in smaller pieces for ease of transport. New to git use in general and still trying to get a firm grip on "best practices"

    Thanks again for the feedback

    Cheers,

    Frankie

  7. Log in to comment