On Fri, 9 Nov 2007, Jon Smirl wrote: > On 11/9/07, Junio C Hamano <gitster@xxxxxxxxx> wrote: > > "Jon Smirl" <jonsmirl@xxxxxxxxx> writes: > > > > > On 11/9/07, Jon Smirl <jonsmirl@xxxxxxxxx> wrote: > > >> I updated both sides to current git and it still fails. How do I debug this? > > >> What's causing this, "error: pack-objects died with strange error"? > > > > > > My remote host is running 2.4.32, is git ok on that kernel? > > > > No problem that I am aware of. We are not *that* intimate with > > the kernel. > > > > Do "git-fsck --full" on both repositories pass? > > I've just discovered that the hosting company has a mechanism for > killing processes that it believes are consuming too much memory. When > git does it's mmap's it looks like it is using over 512MB of memory > which causes it to get zapped. At least I think this is what is > happening. You might be interested by the following config variables: core.packedGitWindowSize core.packedGitLimit core.deltaBaseCacheLimit pack.windowMemory pack.deltaCacheSize Certainly one or more of them could be tweaked in the remote repo to solve your problem. But since your problem happens on push then you should look at the core variables first. Nicolas - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
