zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: "Johan Ström" <johan@stromnet.se>
Cc: Jun T <takimoto-j@kba.biglobe.ne.jp>,
	Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: 5.9 core dumps under zleentry->zleread->zlecore
Date: Fri, 3 Jun 2022 20:32:09 -0700	[thread overview]
Message-ID: <CAH+w=7ZoRUUJT4MO0XMbJZ0w6YvEfAaDzdAm-coqbBj=Hm6Cqw@mail.gmail.com> (raw)
In-Reply-To: <804b3f24-843f-739c-4dcd-fead87cdb9cf@stromnet.se>

On Fri, Jun 3, 2022 at 3:03 AM Johan Ström <johan@stromnet.se> wrote:
>
> The terminals (https://codeberg.org/dnkl/foot) where used a bit on one
> day, then left idle for some days, then as soon as touching it (cannot
> say for sure, up-arrow or enter or something), the zsh process crashed.
> Other terminals with similar workload have remained alive, so it seems
> to be a bit random.

I would start looking for signals that your terminal (or wayland)
might be sending.  E.g., if this happens to windows that were on
different virtual desktops or that were partly or completely hidden
behind other windows or that were minimized and then popped open, the
shell may be getting a lot of SIGWINCH signals.

The other thing I notice is that the configure options in the arch
linux package you used include enabling global startup scripts in
/etc/zsh/, and explicitly enable sourcing /etc/profile.  Is there
anything (else) in your /etc/zsh/ directory?


  reply	other threads:[~2022-06-04  3:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02  7:11 Johan Ström
2022-06-02  7:31 ` Bart Schaefer
2022-06-02  9:25   ` Johan Ström
2022-06-03  7:14 ` Jun T
2022-06-03  7:19   ` Johan Ström
2022-06-03  9:53     ` Jun T
2022-06-03 10:02       ` Johan Ström
2022-06-04  3:32         ` Bart Schaefer [this message]
2022-06-04  7:39           ` Johan Ström
2022-06-04 20:06             ` Bart Schaefer

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=7ZoRUUJT4MO0XMbJZ0w6YvEfAaDzdAm-coqbBj=Hm6Cqw@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=johan@stromnet.se \
    --cc=takimoto-j@kba.biglobe.ne.jp \
    --cc=zsh-workers@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).