From: Johannes Sixt <j.sixt@viscovery.net>
To: kusmabite@gmail.com
Cc: "Vicent Martí" <tanoku@gmail.com>, "Jeff King" <peff@peff.net>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: pack bitmap woes on Windows
Date: Wed, 12 Feb 2014 13:44:10 +0100 [thread overview]
Message-ID: <52FB6C9A.30204@viscovery.net> (raw)
In-Reply-To: <CABPQNSZAK2d1hSQNG6uoNHoTJGCiq2UnaBP+_RJkPi47xaxGPQ@mail.gmail.com>
Am 2/12/2014 12:56, schrieb Erik Faye-Lund:
> On Wed, Feb 12, 2014 at 8:27 AM, Johannes Sixt <j.sixt@viscovery.net> wrote:
>> Running test suite of 'next' on Windows fails in t5310-pack-bitmaps with
>> the following symptoms. I haven't followed the topic. Have there been
>> patches floating that addressed the problem in one way or another?
>>
>> (gdb) run
>> Starting program: D:\Src\mingw-git\t\trash directory.t5310-pack-bitmaps/..\..\git.exe rev-list --test-bitmap HEAD
>> [New thread 3528.0x8d4]
>> Bitmap v1 test (20 entries loaded)
>> Found bitmap for 537ea4d3eb79c95f602873b1167c480006d2ac2d. 64 bits / 15873b36 checksum
>>
>> Breakpoint 1, die (err=0x5939e9 "Out of memory, realloc failed") at usage.c:97
>> 97 if (die_is_recursing()) {
>> (gdb) bt
>> #0 die (err=0x5939e9 "Out of memory, realloc failed") at usage.c:97
>> #1 0x00487c4c in xrealloc (ptr=0x12b10008, size=837107040) at wrapper.c:109
>
> ~800 megs is a pretty large allocation for 32-bit systems. What gives?
That's exactly the problem: why would a tiny repository from the test
suite require such a large allocation? (Not to mention that the allocation
ultimately fails in my case.)
next prev parent reply other threads:[~2014-02-12 12:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 7:27 pack bitmap woes on Windows Johannes Sixt
2014-02-12 11:56 ` Erik Faye-Lund
2014-02-12 12:44 ` Johannes Sixt [this message]
2014-02-12 12:55 ` David Kastrup
2014-02-12 13:05 ` Johannes Sixt
2014-02-12 13:23 ` David Kastrup
2014-02-12 14:09 ` Duy Nguyen
2014-02-12 14:22 ` Erik Faye-Lund
2014-02-12 14:49 ` Erik Faye-Lund
2014-02-12 16:48 ` Jeff King
2014-02-13 8:07 ` Johannes Sixt
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52FB6C9A.30204@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=kusmabite@gmail.com \
--cc=peff@peff.net \
--cc=tanoku@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.