From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Clemente <n142857@gmail.com>
Cc: 71177@debbugs.gnu.org
Subject: bug#71177: 30.0.50; crash when opening and closing many TTY frames in succession
Date: Fri, 24 May 2024 22:31:49 +0300 [thread overview]
Message-ID: <86o78v0zx6.fsf@gnu.org> (raw)
In-Reply-To: <CAJKAhPB1wO9bJwm0vTeWngEn8-p7p7rH4XMpLWxf3v+nPXh2QA@mail.gmail.com> (message from Daniel Clemente on Fri, 24 May 2024 17:47:27 +0000)
> From: Daniel Clemente <n142857@gmail.com>
> Date: Fri, 24 May 2024 17:47:27 +0000
>
> Emacs compiled without X.
> I can launch a new emacsclient with a keypress and I can kill it with another keypress.
> I held down the key to launch many emacsclient (around 20), then killed them, then launched a few more,
> killed them, … Less than 10 seconds of this behaviour are enough to crash the server.
> This doesn't happen during normal usage. I was intentionally trying to find the bug. I don't expect the daemon
> to crash only by opening/closing frames.
> The command I run to launch the emacsclient is: emacsclient -c -e "(progn (dired "~"))"
> I use rxvt-unicode.
>
> Program received signal SIGPIPE, Broken pipe.
I think it crashes because of this SIGPIPE. I hope some Unix expert
will be able to explain why Emacs gets get SIGPIPE in this scenario.
Perhaps because you kill emacsclient too quickly?
It might help if you post the details of how you "launch a new
emacsclient with a keypress and kill it with another keypress". IOW,
please describe the recipe to reproduce the problem starting from
"emacs -Q -nw --daemon".
Thanks.
next prev parent reply other threads:[~2024-05-24 19:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 17:47 bug#71177: 30.0.50; crash when opening and closing many TTY frames in succession Daniel Clemente
2024-05-24 19:31 ` Eli Zaretskii [this message]
2024-05-25 0:37 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-25 11:04 ` Daniel Clemente
2024-05-25 12:43 ` Eli Zaretskii
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=86o78v0zx6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71177@debbugs.gnu.org \
--cc=n142857@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.