git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "René Scharfe" <l.s.r@web.de>
To: Carsten Fuchs <carsten.fuchs@cafu.de>, git@vger.kernel.org
Subject: Re: git status --> Out of memory, realloc failed
Date: Wed, 1 Mar 2017 11:02:51 +0100	[thread overview]
Message-ID: <ea0722e2-c2bd-bd80-a233-50676efcafda@web.de> (raw)
In-Reply-To: <84c02ca1-269e-2f26-c625-476d7f087f5c@cafu.de>

Am 25.02.2017 um 11:13 schrieb Carsten Fuchs:
> Dear Git group,
>
> I use Git at a web hosting service, where my user account has a memory
> limit of 768 MB:
>
> (uiserver):p7715773:~$ uname -a
> Linux infongp-de15 3.14.0-ui16322-uiabi1-infong-amd64 #1 SMP Debian
> 3.14.79-2~ui80+4 (2016-11-17) x86_64 GNU/Linux

What's the output of "ulimit -a"?

> (uiserver):p7715773:~$ git --version
> git version 2.1.4

That's quite old.  Can you try a more recent version easily (2.12.0 just 
came out)?  I don't remember a specific fix, and memory usage perhaps 
even increased with newer versions, but ruling out already fixed issues 
would be nice.

> (uiserver):p7715773:~/cafu$ git gc
> Zähle Objekte: 44293, Fertig.
> Komprimiere Objekte: 100% (24534/24534), Fertig.
> Schreibe Objekte: 100% (44293/44293), Fertig.
> Total 44293 (delta 17560), reused 41828 (delta 16708)
>
> (uiserver):p7715773:~/cafu$ git status
> fatal: Out of memory, realloc failed
> fatal: recursion detected in die handler
>
> The repository is tracking about 19000 files which together take 260 MB.
> The git server version is 2.7.4.1.g5468f9e (Bitbucket)

Is your repository publicly accessible?

René

  reply	other threads:[~2017-03-01 10:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-25 10:13 git status --> Out of memory, realloc failed Carsten Fuchs
2017-03-01 10:02 ` René Scharfe [this message]
2017-03-01 20:12   ` Carsten Fuchs
2017-03-02  9:31     ` Duy Nguyen
2017-03-03 21:10       ` Carsten Fuchs
2017-03-02 20:04     ` René Scharfe
2017-03-03 21:03       ` Carsten Fuchs

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ea0722e2-c2bd-bd80-a233-50676efcafda@web.de \
    --to=l.s.r@web.de \
    --cc=carsten.fuchs@cafu.de \
    --cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).