From: "René Scharfe" <l.s.r@web.de>
To: Carsten Fuchs <carsten.fuchs@cafu.de>
Cc: git@vger.kernel.org
Subject: Re: git status --> Out of memory, realloc failed
Date: Thu, 2 Mar 2017 21:04:12 +0100 [thread overview]
Message-ID: <6ba86c1a-87a9-f886-273b-7f94c30c4a95@web.de> (raw)
In-Reply-To: <cbd281fc-3a4b-b4dc-5dff-145c97cd68d6@cafu.de>
Am 01.03.2017 um 21:12 schrieb Carsten Fuchs:
> Hi René,
>
> Am 01.03.2017 um 11:02 schrieb René Scharfe:
>>> 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:~$ ulimit -a
> core file size (blocks, -c) 0
> data seg size (kbytes, -d) unlimited
> scheduling priority (-e) 1
> file size (blocks, -f) unlimited
> pending signals (-i) 16382
> max locked memory (kbytes, -l) 64
> max memory size (kbytes, -m) unlimited
> open files (-n) 512
> pipe size (512 bytes, -p) 8
> POSIX message queues (bytes, -q) 819200
> real-time priority (-r) 0
> stack size (kbytes, -s) 8192
> cpu time (seconds, -t) 1800
> max user processes (-u) 42
> virtual memory (kbytes, -v) 786432
> file locks (-x) unlimited
When I use ulimit -v with lower and lower numbers I can provoke mmap
failures on bigger pack files, but not the realloc failures that you're
seeing. And your packs should be only up to 20MB anyway (you can check
that with "ls -l .git/objects/pack/*.pack").
>>> 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?
>
> Unfortunately, no. There are no big secrets in there, but just a couple
> of database details so that I cannot make it universally available. I
> can gladly give you access though. (E.g. by adding your public SSH key?)
I'd rather not look at semi-confidential data, and you probably
shouldn't hand it to a stranger on the internet anyway. ;)
So a shot in the dark: Do you have a lot of untracked files? You could
check by cloning your repository locally (which copies only tracked
contents). Does "git status" work on the clone?
Another one, darker yet: Does "git config core.preloadIndex 0" help?
René
next prev parent reply other threads:[~2017-03-02 20: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
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 [this message]
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=6ba86c1a-87a9-f886-273b-7f94c30c4a95@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).