From: Bart Schaefer <schaefer@brasslantern.com>
To: "Johan Ström" <johan@stromnet.se>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: "crash: free invalid next size (fast)" on completion
Date: Wed, 23 Mar 2022 10:14:44 -0700 [thread overview]
Message-ID: <CAH+w=7Yn_jyvHiOtpMAmq8rFESM16LgEdzgGx7t0E+c2ctS1fg@mail.gmail.com> (raw)
In-Reply-To: <df2ea61b-d0ea-ba95-98e0-d0fe84b800d0@stromnet.se>
(Following up to zsh-users so this thread doesn't appear abandoned;
further discussion should probably be directed to
zsh-workers@zsh.org.)
On Tue, Mar 22, 2022 at 12:41 AM Johan Ström <johan@stromnet.se> wrote:
>
> last week (and now today again, on several terminals after being idle since Friday) I noticed that several of my terminals crashed and closed when writing `git <tab>` or `ls <tab>`. Managed to capture one such crash on video before terminal closed, and it printed "free invalid next size (fast)".
...
> Stack trace of thread 843836:
> #5 0x00007f36842f104d _int_free (libc.so.6 + 0x9b04d)
> #6 0x00007f36842f3be3 free (libc.so.6 + 0x9dbe3)
> #7 0x00007f36839ffa7f unmetafy_line (zle.so + 0x33a7f)
> #8 0x00007f3683a0427a n/a (zle.so + 0x3827a)
> #9 0x00007f36839fcc34 completecall (zle.so + 0x30c34)
>
> These terminals have been running for ~5 days.
> On newly opened terminals, tab completion works fine.
>
> Have had 5.8-1 on this machine since July, never had any issues. 5.8.1-1 installed on 16 Feb.
Hm. There's nothing in the zsh code changes I see that would cause
this effect; an actually idle shell should have been sitting blocked
on read. Is there any sort of periodic event that might be sending a
signal to those shells?
Do other completions crash, or only completions that involve file names?
prev parent reply other threads:[~2022-03-23 17:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 7:41 Johan Ström
2022-03-23 17:14 ` Bart Schaefer [this message]
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='CAH+w=7Yn_jyvHiOtpMAmq8rFESM16LgEdzgGx7t0E+c2ctS1fg@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=johan@stromnet.se \
--cc=zsh-users@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).