Re: Crash when pushing large binary file

From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date: Nov 20, 2012, 11:37 UTC
Message-ID: <CACsJy8Ai=JK8c5GbjXBY2A4mtxSUUTzrTJt=puxXvDD1fhFmFg@mail.gmail.com>
In-Reply-To: <CA+AoP-n=P3-yTshfQRwdyUcb7eFM12-+bAtS_FUAxXtwuFxjzg@mail.gmail.com>

On Tue, Nov 20, 2012 at 8:50 AM, Thomas Gay <tgay@tokyois.com> wrote:

Show 17 quoted lines

> Sorry for the late reply; I've been out of the office for the past few days.
>
> On Fri, Nov 16, 2012 at 7:11 PM, Nguyen Thai Ngoc Duy <pclouds@gmail.com> wrote:
>> If it still says "unpack-objects died of signal 11" then it was not
>> done the right way.
>
> I upgraded Git on both ends and tried setting it again. index-pack was
> used this time, but it still failed:
>
> Counting objects: 38, done.
> Delta compression using up to 4 threads.
> Compressing objects: 100% (26/26), done.
> error: index-pack died of signal 11 GiB | 62.44 MiB/s
> error: pack-objects died of signal 13
> error: failed to push some refs to '...'
>
> Would you still like me to try your other method?

Interesting. No, if index-pack fails too the culprit is something else. Does the stack trace look the same (i.e. crashed in write_sha1_file_prepare)? I still don't know how it crashes there. It'd be great if you could run it under valgrind (not sure if valgrind runs in OS X). Try building with NO_OPENSSL too to avoid external sha1 issues.

-- 
Duy