zsh-workers
 help / color / mirror / code / Atom feed
From: "Johan Ström" <johan@stromnet.se>
To: Jun T <takimoto-j@kba.biglobe.ne.jp>, zsh-workers@zsh.org
Subject: Re: 5.9 core dumps under zleentry->zleread->zlecore
Date: Fri, 3 Jun 2022 12:02:53 +0200	[thread overview]
Message-ID: <804b3f24-843f-739c-4dcd-fead87cdb9cf@stromnet.se> (raw)
In-Reply-To: <3CAEF71A-E8AD-47A8-A295-BFA58F453E79@kba.biglobe.ne.jp>


On 2022-06-03 11:53, Jun T wrote:
>> 2022/06/03 16:19, Johan Ström <johan@stromnet.se> wrote:
>>
>> Yes, full system update including reboot:
> Hmm, then:
>
> pacman -Syu
> Reboot.
> Start a new zsh, leave it for a few days, and then it cashes.
> After the crash, start another zsh, but it doesn't crash.
>
> Is this what happening to you?

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. All terminals where probably started around the same 
time (i.e. similar history file read in?), but cannot say for sure.
Not same commands executed in them, most work in them are of the 
"up-arrow/search-in-history -re-execute" style, but of course some "new" 
commands executed too.

No other process crashes / problems indicating machine-wide issues.

It doesn't happen super often, but every now and then:

$ coredumpctl |grep -E 'zsh|TIME'
TIME                             PID  UID  GID SIG     COREFILE EXE SIZE
Tue 2022-03-01 08:44:43 CET  1530870 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Fri 2022-03-04 08:29:11 CET  1530829 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Fri 2022-03-04 09:28:11 CET  2161402 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-03-15 08:29:04 CET  2080740 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-03-15 08:29:28 CET   844046 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-03-15 08:29:34 CET   881888 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-03-15 08:30:03 CET   843836 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-03-15 08:45:46 CET   987956 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-03-15 09:12:02 CET   835401 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-03-22 07:37:58 CET  2751972 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-03-22 07:38:50 CET   636567 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-03-22 08:40:14 CET   505887 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-04-12 07:48:54 CEST 2560148 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-04-12 09:28:53 CEST  845636 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-04-19 08:41:26 CEST 2828220 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-04-19 08:41:36 CEST  506222 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Mon 2022-05-02 06:55:52 CEST 1776915 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-05-24 07:32:32 CEST 2358112 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-05-24 08:12:13 CEST 1088984 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Tue 2022-05-24 10:16:54 CEST 2983454 1000 1001 SIGABRT missing 
/usr/bin/zsh n/a
Thu 2022-06-02 07:37:08 CEST 2195627 1000 1001 SIGABRT present 
/usr/bin/zsh 449.7K
Thu 2022-06-02 08:27:39 CEST 1097282 1000 1001 SIGABRT present 
/usr/bin/zsh 411.2K



  reply	other threads:[~2022-06-03 10:03 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 [this message]
2022-06-04  3:32         ` Bart Schaefer
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=804b3f24-843f-739c-4dcd-fead87cdb9cf@stromnet.se \
    --to=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).