Git development
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: "René Scharfe" <l.s.r@web.de>, "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: Mon, 18 Nov 2024 09:19:04 +0100	[thread overview]
Message-ID: <Zzr4cgk_5MJNcHm1@pks.im> (raw)
In-Reply-To: <xmqq34js1kd2.fsf@gitster.g>

On Sat, Nov 16, 2024 at 02:23:53AM +0900, Junio C Hamano wrote:
> René Scharfe <l.s.r@web.de> writes:
> 
> > 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.
> 
> Thanks.
> 
> There are bunch of topics that could go to 'maint' and be part of a
> maintenance topic, and this certainly looks like one of those topics
> that can go into 2.47.1 someday.  The usual source of candidate
> topics I use is messy and unusable for some unknown reason, but
> offhand I think these are safe and sensible to merge down to
> 'maint':
> 
>     ds/line-log-asan-fix # 1 (2024-10-10) 
>     jk/fsmonitor-event-listener-race-fix # 2 (2024-10-15) 
>     ps/maintenance-start-crash-fix # 1 (2024-10-18) 

Other candidates that fix regressions:

    jk/fetch-prefetch-double-free-fix
    tb/multi-pack-reuse-dupfix
    pb/clar-build-fix
    ps/upgrade-clar
    wm/shortlog-hash

I think that we have accumulated enough topics by now to warrant a
2.47.1 release, but will of course leave that decision to you.

Thanks!

Patrick

  reply	other threads:[~2024-11-18  8:19 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
2024-11-15 17:23   ` Junio C Hamano
2024-11-18  8:19     ` Patrick Steinhardt [this message]
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=Zzr4cgk_5MJNcHm1@pks.im \
    --to=ps@pks.im \
    --cc=ak@enrg8.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=l.s.r@web.de \
    /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