Re: [git-users] git checkout crashes after server being updated to Debian X86_64

2016-10-18 Thread Konstantin Khomoutov 
On Tue, 18 Oct 2016 07:56:31 -0700 (PDT)
Raffael Reichelt  wrote:

> 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.
[...]
> 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

Please bring this on the main Git list (see [1]).
We here merely deal with usage issues but you appear to had hit
something serious.

1. https://gist.github.com/tfnico/4441562

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[git-users] git checkout crashes after server being updated to Debian X86_64

2016-10-18 Thread 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): 0x00a8ade0 
***

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?


Regards,

Raffael

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.