Git development
 help / color / mirror / Atom feed
From: "René Scharfe" <l.s.r@web.de>
To: Attila Kerekes <ak@enrg8.com>, git@vger.kernel.org
Subject: Re: malloc: *** error for object 0x1: pointer being freed was not allocated on MacOS with git 2.47.0
Date: Fri, 15 Nov 2024 17:34:16 +0100	[thread overview]
Message-ID: <4ca84916-c5f5-4d52-8f6a-08b729bb66b8@web.de> (raw)
In-Reply-To: <5FFE9429-7496-429F-BEC5-9D00C8409AC3@enrg8.com>

Am 15.11.24 um 10:40 schrieb Attila Kerekes:
> Dear Maintainers!
>
> See my bug report below:
>
> What did you do before the bug happened? (Steps to reproduce your issue)
>
> run the command:
>   git maintenance start
>
> What did you expect to happen? (Expected behavior)
>
> git maintenance is started
>
> What happened instead? (Actual behavior)
>
> git(26100,0x1ffd63840) malloc: *** error for object 0x1: pointer being freed was not allocated
>
> What's different between what you expected and what actually happened?
>
> git maintenance jobs did not get set up, instead i got a malloc error

This is a known error.  Commit c95547a394 (builtin/gc: fix crash when
running `git maintenance start`, 2024-10-10) fixes it, but has not made
it into a released version, yet.

René


  reply	other threads:[~2024-11-15 16:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-15  9:40 malloc: *** error for object 0x1: pointer being freed was not allocated on MacOS with git 2.47.0 Attila Kerekes
2024-11-15 16:34 ` René Scharfe [this message]
2024-11-15 17:23   ` Junio C Hamano
2024-11-18  8:19     ` Patrick Steinhardt
2024-11-18 12:42       ` Junio C Hamano
2024-11-18 13:07         ` Patrick Steinhardt
2024-11-18 23:51           ` Junio C Hamano
2024-11-18 19:28         ` Philippe Blain
2024-11-19  0:33           ` Junio C Hamano

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=4ca84916-c5f5-4d52-8f6a-08b729bb66b8@web.de \
    --to=l.s.r@web.de \
    --cc=ak@enrg8.com \
    --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