From: Martin Englund <martin@englund.nu>
To: git@vger.kernel.org
Subject: Git Bug Report: out of memory using git tag
Date: Fri, 28 Oct 2022 15:29:33 -0700 [thread overview]
Message-ID: <CABYbkvP=fMmaFUD3bQbeQ-XKiMSP6g-u0p7Vq1Qt_K5=D5WJ+A@mail.gmail.com> (raw)
Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.
What did you do before the bug happened? (Steps to reproduce your issue)
I created a signed tag (git tag -s) using a ssh-agent key and then ran
git tag -l --format '%(contents:body)' v0.6.1
What did you expect to happen? (Expected behavior)
I get the output
What happened instead? (Actual behavior)
fatal: Out of memory, malloc failed (tried to allocate
18446744073709551266 bytes)
What's different between what you expected and what actually happened?
git tries to allocate an unreasonable amount of memory
Anything else you want to add:
I don't have 18,000 PB of memory
Please review the rest of the bug report below.
You can delete any lines you don't wish to share.
[System Info]
git version:
git version 2.38.1.280.g63bba4fdd8
cpu: x86_64
built from commit: 63bba4fdd86d80ef061c449daa97a981a9be0792
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: Linux 5.15.0-1021-aws #25~20.04.1-Ubuntu SMP Thu Sep 22
13:59:08 UTC 2022 x86_64
compiler info: gnuc: 9.4
libc info: glibc: 2.31
$SHELL (typically, interactive shell): /bin/bash
Cheers,
/Martin
--
Martin Englund, martin@englund.nu / GnuPG key: FE91E717
http://blog.englund.nu/
next reply other threads:[~2022-10-28 22:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 22:29 Martin Englund [this message]
2022-11-01 12:22 ` Git Bug Report: out of memory using git tag Jeff King
2022-11-02 0:41 ` Philippe Blain
2022-11-02 7:39 ` Jeff King
2022-11-02 7:42 ` [PATCH 1/2] ref-filter: fix parsing of signatures without blank lines Jeff King
2022-11-02 7:44 ` [PATCH 2/2] ref-filter: fix parsing of signatures with CRLF and no body Jeff King
2022-11-02 8:14 ` Git Bug Report: out of memory using git tag Elijah Newren
2022-11-02 9:13 ` gigantic commit messages, was " Jeff King
2022-11-02 14:26 ` Ævar Arnfjörð Bjarmason
2022-11-02 15:43 ` Elijah Newren
2022-11-02 8:24 ` Eric Sunshine
2022-11-02 12:13 ` Philippe Blain
2022-11-03 4:32 ` Jeff King
2022-11-03 0:42 ` Taylor Blau
2022-11-02 0:42 ` Philippe Blain
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='CABYbkvP=fMmaFUD3bQbeQ-XKiMSP6g-u0p7Vq1Qt_K5=D5WJ+A@mail.gmail.com' \
--to=martin@englund.nu \
--cc=git@vger.kernel.org \
/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 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 NNTP newsgroup(s).