From: "René Scharfe" <l.s.r@web.de>
To: Raffael Reichelt <raffael.reichelt@gmail.com>, git@vger.kernel.org
Subject: Re: git checkout crashes after server being updated to Debian X86_64
Date: Tue, 18 Oct 2016 18:42:07 +0200 [thread overview]
Message-ID: <1c70da04-d26b-f0af-8939-edc96de586d9@web.de> (raw)
In-Reply-To: <6B2BE996-F696-4EB4-91CA-849D40B8802D@gmail.com>
Am 18.10.2016 um 17:17 schrieb Raffael Reichelt:
> Hello!
>
> I have a serious problem with git, After my provider had updated to a
> X86_64 architecture git crashes with various memory-related errors.
> This is happening remote when pushing to the repository from my local
> machine as well as trying it on a shell on the server itself.
>
> This are the error-messages:
>
> fatal: Out of memory, realloc failed
> fatal: recursion detected in die handler
> fatal: recursion detected in die handler
>
> or
> fatal: unable to create threaded lstat
> fatal: recursion detected in die handler
> or
> fatal: unable to create threaded lstat
> *** Error in `git': double free or corruption (fasttop): 0x0000000000a8ade0 ***
> fatal: recursion detected in die handler
> Aborted
>
> It’s obviously not a problem of the repository - happens with all of
> them. I think it is also not a question of size - happens with a 80M
> Repository as well as with a 500M one.
>
> Any way: did a
>
> git fsck
> Prüfe Objekt-Verzeichnisse: 100% (256/256), Fertig.
> Prüfe Objekte: 100% (56305/56305), Fertig.
>
> git gc --auto --prune=today —aggressive
> git repack
>
> Additionally I played around some config parameters so my config now looks like:
> [http]
> postbuffer = 524288000
> [pack]
> threads = 1
> deltaCacheSize = 128m
> packSizeLimit = 128m
> windowMemory = 128m
> [core]
> packedGitLimit = 128m
> packedGitWindowSize = 128m
> repositoryformatversion = 0
> filemode = true
> bare = true
>
> I am running
> git version 2.1.4
>
> on
> Linux infongp-de65 3.14.0-ui16196-uiabi1-infong-amd64 #1 SMP Debian 3.14.73-2~ui80+4 (2016-07-13) x86_64 GNU/Linux
>
> Anyone out there to help me getting out of this trouble?
Git 2.1.4 is the version that comes with Debian stable according to
https://packages.debian.org/jessie/git, so I guess using a more recent
version is not a reasonable option.
What do "file $(which git)" and "ulimit -a" return? Do you have an
x86-64 binary and no unnecessarily low limits set?
René
next prev parent reply other threads:[~2016-10-18 16:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 15:17 git checkout crashes after server being updated to Debian X86_64 Raffael Reichelt
2016-10-18 16:42 ` René Scharfe [this message]
2016-10-18 17:00 ` Raffael Reichelt
2016-10-19 13:27 ` Duy Nguyen
2016-10-19 13:47 ` [PATCH] Add a knob to abort on die() (was Re: git checkout crashes after ...) Duy Nguyen
2016-10-19 21:15 ` Jeff King
2016-10-19 14:05 ` git checkout crashes after server being updated to Debian X86_64 Raffael Reichelt
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=1c70da04-d26b-f0af-8939-edc96de586d9@web.de \
--to=l.s.r@web.de \
--cc=git@vger.kernel.org \
--cc=raffael.reichelt@gmail.com \
/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).