bug#50252: 28.0.50; Emacs crashed when daemon could not access it

bug#50252: 28.0.50; Emacs crashed when daemon could not access it

[bugs]

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



In GNU Emacs 28.0.50 (build 4, x86_64-pc-linux-gnu, X toolkit, cairo version 1.17.4, Xaw3d scroll bars)
 of 2021-07-28 built on protected.rcdrun.com
Repository revision: 2910e668eb95b35a2854426c1e6ef0137da578a4
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12011000
System Description: Parabola GNU/Linux-libre

Configured using:
 'configure --with-x-toolkit=lucid'

Configured features:
ACL CAIRO DBUS FREETYPE GIF GLIB GMP GNUTLS GPM GSETTINGS HARFBUZZ JPEG
JSON LCMS2 LIBOTF LIBSYSTEMD LIBXML2 M17N_FLT MODULES NOTIFY INOTIFY
PDUMPER PNG RSVG SECCOMP SOUND THREADS TIFF TOOLKIT_SCROLL_BARS X11
XAW3D XDBE XIM XPM LUCID ZLIB

Important settings:
  value of $LC_ALL: en_US.UTF-8
  value of $LANG: de_DE.UTF-8
  value of $XMODIFIERS: @im=exwm-xim
  locale-coding-system: utf-8-unix

Major mode: Lisp Interaction

Minor modes in effect:
  tooltip-mode: t
  global-eldoc-mode: t
  eldoc-mode: t
  electric-indent-mode: t
  mouse-wheel-mode: t
  tool-bar-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  line-number-mode: t
  indent-tabs-mode: t
  transient-mark-mode: t

Load-path shadows:
None found.

Features:
(shadow sort mail-extr emacsbug message rmc puny dired dired-loaddefs
rfc822 mml mml-sec epa derived epg epg-config gnus-util rmail
rmail-loaddefs auth-source cl-seq eieio eieio-core cl-macs
eieio-loaddefs password-cache json map text-property-search time-date
subr-x seq byte-opt gv bytecomp byte-compile cconv mm-decode mm-bodies
mm-encode mail-parse rfc2231 mailabbrev gmm-utils mailheader cl-loaddefs
cl-lib sendmail rfc2047 rfc2045 ietf-drums mm-util mail-prsvr mail-utils
iso-transl tooltip eldoc electric uniquify ediff-hook vc-hooks
lisp-float-type mwheel term/x-win x-win term/common-win x-dnd tool-bar
dnd fontset image regexp-opt fringe tabulated-list replace newcomment
text-mode elisp-mode lisp-mode prog-mode register page tab-bar menu-bar
rfn-eshadow isearch easymenu timer select scroll-bar mouse jit-lock
font-lock syntax font-core term/tty-colors frame minibuffer cl-generic
cham georgian utf-8-lang misc-lang vietnamese tibetan thai tai-viet lao
korean japanese eucjp-ms cp51932 hebrew greek romanian slovak czech
european ethiopic indian cyrillic chinese composite charscript charprop
case-table epa-hook jka-cmpr-hook help simple abbrev obarray
cl-preloaded nadvice button loaddefs faces cus-face macroexp files
window text-properties overlay sha1 md5 base64 format env code-pages
mule custom widget hashtable-print-readable backquote threads dbusbind
inotify lcms2 dynamic-setting system-font-setting font-render-setting
cairo x-toolkit x multi-tty make-network-process emacs)

Memory information:
((conses 16 54546 6421)
 (symbols 48 7151 3)
 (strings 32 20072 1907)
 (string-bytes 1 642017)
 (vectors 16 14218)
 (vector-slots 8 185689 9607)
 (floats 8 23 35)
 (intervals 56 263 0)
 (buffers 992 12))

-- 
Thanks,
Jean Louis

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

bug#50252: 28.0.50; Emacs crashed when daemon could not access it

[Eli Zaretskii]

> 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?

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?

Bottom line: I'm confused by the report, please clarify.

bug#50252: 28.0.50; Emacs crashed when daemon could not access it

[Lars Ingebrigtsen]

Eli Zaretskii <eliz@gnu.org> writes:

> Bottom line: I'm confused by the report, please clarify.

More information was requested, but no response was given within a
month, so I'm closing this bug report.  If the problem still exists,
please respond to this email and we'll reopen the bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#50252: 28.0.50; Emacs crashed when daemon could not access it

[Jean Louis]

* 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

bug#50252: 28.0.50; Emacs crashed when daemon could not access it

[Eli Zaretskii]

> Date: Mon, 27 Sep 2021 17:15:52 +0300
> From: Jean Louis <bugs@gnu.support>
> Cc: 50252@debbugs.gnu.org
> 
> > 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.

OK, thanks for clarifying.  The situation is now quite clear, I think,
but to make any progress with this bug, we'd need either some kind of
backtrace from the crash, or a reproducible recipe.  And I understand
neither is available?