unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 50252@debbugs.gnu.org
Subject: bug#50252: 28.0.50; Emacs crashed when daemon could not access it
Date: Mon, 27 Sep 2021 17:15:52 +0300	[thread overview]
Message-ID: <YVHSGD2gAfg8WfV0@protected.localdomain> (raw)
In-Reply-To: <83k0k4l6zp.fsf@gnu.org>

* Eli Zaretskii <eliz@gnu.org> [2021-08-29 16:24]:
> > From: bugs@gnu.support
> > Date: Sun, 29 Aug 2021 16:13:37 +0300
> > 
> > 
> > I cannot reproduce this bug, though I know process which triggered the
> > crash:
> > 
> > - I was using Mutt email client that spawns emacsdaemon
> > 
> > - The main Emacs instance was blocked because I used ! to play video
> > 
> > - When I interrupted playing video, the instance crashed
> 
> Sorry, I don't understand the situation and the sequence of events.
> 
> How many Emacs instances were involved: one or two?  You are talking
> about "emacsdaemon" on the one hand, and "the main Emacs instance"
> OTOH: are those two different and separate Emacs sessions running at
> the same time on the same system?

One instance, and emacsclient.

> And what do you mean when you say in the Subject "Emacs crashed when
> daemon could not access it" -- what is "it" here?  If "it" is Emacs,
> then what do you mean by "daemon accesses it"? how can a daemon access
> Emacs?

Sorry to be late.

Emacs was running as daemon and I had to edit new file with
emacsclient. However, Emacs was busy doing something else in this case
video playing by using `!' so the instance was blocked. Then when
video was interrupted, Emacs crushed completely in the memory.

Jean





  parent reply	other threads:[~2021-09-27 14:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-29 13:13 bug#50252: 28.0.50; Emacs crashed when daemon could not access it bugs
2021-08-29 13:23 ` Eli Zaretskii
2021-09-27 10:49   ` Lars Ingebrigtsen
2021-09-27 14:15   ` Jean Louis [this message]
2021-09-27 15:24     ` 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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YVHSGD2gAfg8WfV0@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=50252@debbugs.gnu.org \
    --cc=eliz@gnu.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.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).