GNU bug report logs - #34059
27.0.50; Emacs hangs on typing quit (MS-Windows)

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 34059 in the body.
You can then email your comments to 34059 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Richard Copley <rcopley <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 27.0.50; Emacs hangs on typing quit (MS-Windows)
Date: Sun, 13 Jan 2019 13:04:05 +0000

Emacs sometimes hangs on typing quit, on MS-Windows. (See also
<https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25279#69>.)

A backtrace:

Thread 6 (Thread 2912.0x23b4):
#0  0x00007ffaccb3e371 in ntdll!DbgBreakPoint () from
C:\WINDOWS\SYSTEM32\ntdll.dll
No symbol table info available.
#1  0x00007ffaccb694cb in ntdll!DbgUiRemoteBreakin () from
C:\WINDOWS\SYSTEM32\ntdll.dll
No symbol table info available.
#2  0x00007ffacbf43034 in KERNEL32!BaseThreadInitThunk () from
C:\WINDOWS\System32\kernel32.dll
No symbol table info available.
#3  0x00007ffaccb13691 in ntdll!RtlUserThreadStart () from
C:\WINDOWS\SYSTEM32\ntdll.dll
No symbol table info available.
#4  0x0000000000000000 in ?? ()
No symbol table info available.
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 5 (Thread 2912.0x2d84):
#0  0x00007ffaccb3aa64 in ntdll!ZwReadFile () from C:\WINDOWS\SYSTEM32\ntdll.dll
No symbol table info available.
#1  0x00007ffac90b2b36 in ReadFile () from C:\WINDOWS\System32\KernelBase.dll
No symbol table info available.
#2  0x00007ffacc15e3b2 in msvcrt!_read () from C:\WINDOWS\System32\msvcrt.dll
No symbol table info available.
#3  0x00007ffacc15e09b in msvcrt!_read () from C:\WINDOWS\System32\msvcrt.dll
No symbol table info available.
#4  0x0000000400286f2b in _sys_read_ahead (fd=6) at w32.c:8461
        cp = 0x401e0d720 <child_procs+288>
        rc = 0
#5  0x0000000400290e33 in reader_thread (arg=0x401e0d720
<child_procs+288>) at w32proc.c:1152
        rc = 3
        cp = 0x401e0d720 <child_procs+288>
#6  0x00007ffacbf43034 in KERNEL32!BaseThreadInitThunk () from
C:\WINDOWS\System32\kernel32.dll
No symbol table info available.
#7  0x00007ffaccb13691 in ntdll!RtlUserThreadStart () from
C:\WINDOWS\SYSTEM32\ntdll.dll
No symbol table info available.
#8  0x0000000000000000 in ?? ()
No symbol table info available.
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 4 (Thread 2912.0xa60):
#0  0x00007ffaccb3aa24 in ntdll!ZwWaitForSingleObject () from
C:\WINDOWS\SYSTEM32\ntdll.dll
No symbol table info available.
#1  0x00007ffac90b9252 in WaitForSingleObjectEx () from
C:\WINDOWS\System32\KernelBase.dll
No symbol table info available.
#2  0x000000040028736a in _sys_wait_accept (fd=4) at w32.c:8565
        hEv = 0x630
        cp = 0x401e0d600 <child_procs>
        rc = 258
#3  0x0000000400290e21 in reader_thread (arg=0x401e0d600
<child_procs>) at w32proc.c:1150
        rc = 3
        cp = 0x401e0d600 <child_procs>
#4  0x00007ffacbf43034 in KERNEL32!BaseThreadInitThunk () from
C:\WINDOWS\System32\kernel32.dll
No symbol table info available.
#5  0x00007ffaccb13691 in ntdll!RtlUserThreadStart () from
C:\WINDOWS\SYSTEM32\ntdll.dll
No symbol table info available.
#6  0x0000000000000000 in ?? ()
No symbol table info available.
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 3 (Thread 2912.0x4d4):
#0  0x00007ffaccb3e294 in ntdll!ZwWaitForAlertByThreadId () from
C:\WINDOWS\SYSTEM32\ntdll.dll
No symbol table info available.
#1  0x00007ffaccac4c73 in ntdll!TpSetWait () from C:\WINDOWS\SYSTEM32\ntdll.dll
No symbol table info available.
#2  0x00007ffaccac4a74 in ntdll!TpSetWait () from C:\WINDOWS\SYSTEM32\ntdll.dll
No symbol table info available.
#3  0x00007ffaccabefb7 in ntdll!RtlEnterCriticalSection () from
C:\WINDOWS\SYSTEM32\ntdll.dll
No symbol table info available.
#4  0x00007ffaccabeed0 in ntdll!RtlEnterCriticalSection () from
C:\WINDOWS\SYSTEM32\ntdll.dll
No symbol table info available.
#5  0x0000000400272a15 in post_msg (lpmsg=0x5cbf840) at w32xfns.c:309
        lpNew = 0xd500c0
#6  0x000000040024690b in my_post_msg (wmsg=0x5cbf840, hwnd=0x240608,
msg=0, wParam=103, lParam=2228225) at w32fns.c:2429
No locals.
#7  0x000000040024863d in post_character_message (hwnd=0x240608,
msg=0, wParam=103, lParam=2228225, modifiers=67108864) at
w32fns.c:3559
        wmsg = {msg = {hwnd = 0x240608, message = 0, wParam = 103,
lParam = 2228225, time = 322841890, pt = {x = 0, y = 1072445}},
dwModifiers = 67108864, rect = {left = 4, top = 2394291, right =
67108864, bottom = 1}}
#8  0x000000040024a0f6 in w32_wnd_proc (hwnd=0x240608, msg=258,
wParam=103, lParam=2228225) at w32fns.c:4436
        f = 0xd4e650
        dpyinfo = 0x4007009e0 <one_w32_display_info>
        wmsg = {msg = {hwnd = 0x0, message = 0, wParam = 14129792,
lParam = 140715109885528, time = 14131616, pt = {x = 0, y = 1376765}},
dwModifiers = 0, rect = {left = 0, top = 0, right = 0, bottom = 0}}
        windows_translate = 0
        key = 14014384
#9  0x00007ffacbdb6d41 in USER32!CallWindowProcW () from
C:\WINDOWS\System32\user32.dll
No symbol table info available.
#10 0x00007ffacbdb6713 in USER32!DispatchMessageW () from
C:\WINDOWS\System32\user32.dll
No symbol table info available.
#11 0x00000004002481f9 in w32_msg_pump (msg_buf=0x5cbfec0) at w32fns.c:3355
        msg = {hwnd = 0x240608, message = 256, wParam = 71, lParam =
2228225, time = 322841890, pt = {x = 905, y = 747}}
        result = 0
        focus_window = 0x7ffacbdc8d97 <USER32!PostThreadMessageA+103>
#12 0x00000004002484f3 in w32_msg_worker (arg=0x0) at w32fns.c:3483
        msg = {hwnd = 0x0, message = 0, wParam = 0, lParam = 0, time =
0, pt = {x = 0, y = 0}}
        dummy_buf = {next = 0x0, w32msg = {msg = {hwnd = 0x0, message
= 0, wParam = 0, lParam = 0, time = 0, pt = {x = 0, y = 0}},
dwModifiers = 0, rect = {left = 0, top = 0, right = 0, bottom = 0}},
result = 0, completed = 0}
#13 0x00007ffacbf43034 in KERNEL32!BaseThreadInitThunk () from
C:\WINDOWS\System32\kernel32.dll
No symbol table info available.
#14 0x00007ffaccb13691 in ntdll!RtlUserThreadStart () from
C:\WINDOWS\SYSTEM32\ntdll.dll
No symbol table info available.
#15 0x0000000000000000 in ?? ()
No symbol table info available.
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 2 (Thread 2912.0x1a94):
#0  0x00007ffaccb3b024 in ntdll!ZwDelayExecution () from
C:\WINDOWS\SYSTEM32\ntdll.dll
No symbol table info available.
#1  0x00007ffac90c5e9a in SleepEx () from C:\WINDOWS\System32\KernelBase.dll
No symbol table info available.
#2  0x000000040028fa1a in timer_loop (arg=0x401e0e920 <real_itimer>)
at w32proc.c:383
        sleep_time = 25
        handler = 0x400228957 <handle_alarm_signal>
        now = 13191851913683
        expire = 0
        reload = 0
        itimer = 0x401e0e920 <real_itimer>
        which = 0
        sig = 14
        crit = 0x401e0e9a0 <crit_real>
        max_sleep = 30
        hth = 0x0
#3  0x00007ffacbf43034 in KERNEL32!BaseThreadInitThunk () from
C:\WINDOWS\System32\kernel32.dll
No symbol table info available.
#4  0x00007ffaccb13691 in ntdll!RtlUserThreadStart () from
C:\WINDOWS\SYSTEM32\ntdll.dll
No symbol table info available.
#5  0x0000000000000000 in ?? ()
No symbol table info available.
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 1 (Thread 2912.0x1c54):
#0  0x00007ffac8e796e4 in win32u!NtUserMsgWaitForMultipleObjectsEx ()
from C:\WINDOWS\System32\win32u.dll
No symbol table info available.
#1  0x00007ffacbdc031d in USER32!MsgWaitForMultipleObjectsEx () from
C:\WINDOWS\System32\user32.dll
No symbol table info available.
#2  0x0000000400292f83 in sys_select (nfds=7, rfds=0xbfeab8,
wfds=0xbfeab0, efds=0x0, timeout=0xbfeaa0, ignored=0x0) at
w32proc.c:2313
        orfds = {bits = {81, 0}}
        owfds = {bits = {0, 0}}
        timeout_ms = 100000000
        start_time = 322893906
        i = 7
        nh = 4
        nc = 1
        nr = 0
        active = 1072445
        cp = 0x401e0d570 <event_queue+912>
        cps = {0x401e0d720 <child_procs+288>, 0x0, 0xbfe6c0,
0x40026e52c <w32_read_socket+9147>, 0xbfe710, 0x7ffa00000000, 0x0,
0x0, 0x0, 0x0, 0x0, 0x0, 0x7ffe0358, 0x7ffaccaa7eb3
<ntdll!RtlGetSystemTimePrecise+83>, 0xd566680, 0x40010602c
<XSETCDR+25>, 0xb55d103, 0x4001b2ede <maybe_quit+41>, 0x0, 0x0, 0x10,
0x0, 0xd5, 0x7ffac90d865f
<KERNELBASE!GetSystemTimePreciseAsFileTime+15>, 0x1345ca40228,
0xbfe730, 0xbfe750, 0x7, 0x0, 0x400242a29 <sys_mutex_unlock+25>, 0xd5,
0x0}
        wait_hnd = {0x320, 0x2e8, 0x3f0, 0x4dc, 0x6f0,
0x73007200650073, 0xd464b0, 0x5c007200650074, 0x44007000700041,
0x151980, 0x150cc0, 0x5c006700000006, 0xb0, 0x64002e00730063,
0x6f009a0098, 0xb0, 0xa2, 0x0, 0x8, 0xb, 0x0, 0x0, 0xd20000,
0x7ffaccab922b <ntdll!RtlAllocateHeap+363>, 0x4c00000040, 0x0, 0xa2,
0x0, 0x208, 0x0, 0x2, 0x0, 0x0, 0x0, 0x0, 0x0, 0x9800000000, 0x104,
0x0, 0x0, 0x0, 0x0, 0x54bb92214e57, 0x0, 0x98, 0xbfe898, 0x0,
0x7ffaccbb0330, 0x0, 0x8, 0xa2, 0x7ffaccadd473
<ntdll!RtlDosPathNameToRelativeNtPathName_U_WithStatus+851>, 0x0, 0x0,
0x54bb92214947, 0x0, 0xbfe4f0, 0xbfe510, 0x200000000, 0xbfe530,
0x2080098, 0xbfe530, 0x2, 0x0, 0x0, 0xbfe8e8, 0x55005c003a0063,
0x73007200650073, 0x7300750062005c, 0x5c007200650074,
0x44007000700041, 0x5c006100740061, 0x6d0061006f0052,
0x5c0067006e0069, 0x61006d0065002e, 0x64002e00730063,
0x7400750061005c, 0x610073002d006f, 0x6c002d00650076,
0x5c007400730069, 0x0, 0x7ffac90d95ea <ResetEvent+10>, 0xd5,
0x400272b86 <drain_message_queue+107>, 0x0, 0xbfe630, 0x0, 0x400272978
<get_next_msg+630>, 0x1, 0x0, 0x0, 0x0, 0xbfe630, 0x40011b67a
<unblock_input+24>, 0x0, 0x0}
        fdindex = {-1, 0, 4, 6, 0, 21691, 0, 0, 0, 0, 0, 0, 65, 110,
260, 0, 0, 0, 59926752, 0, 65, 0, 0, 0, -1843311577, 21691,
-861192934, 32762, 110, 0, 12576352, 0, 0, 0, -860159184, 32762, 0, 0,
8, 0, 120, 0, -861023117, 32762, 0, 0, 0, 0, 59926752, 0, 0, 0,
12575488, 0, 12575520, 0, -860641536, 0, 12575552, 0, 34078830, 0,
12575552, 0}
#3  0x0000000400241a2f in really_call_select (arg=0xbfe930) at thread.c:579
        sa = 0xbfe930
        self = 0x4006ffb60 <main_thread>
        oldset = 17180951739
#4  0x000000040018f8a8 in flush_stack_call_func (func=0x40024199d
<really_call_select>, arg=0xbfe930) at alloc.c:5036
        end = 0xbfe8c8
        self = 0x4006ffb60 <main_thread>
        sentry = {o = {__max_align_ll = 0, __max_align_ld = <invalid
float value>}}
#5  0x0000000000000000 in ?? ()
No symbol table info available.
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
[Inferior 1 (process 2912) detached]





In GNU Emacs 27.0.50 (build 1, x86_64-w64-mingw32)
 of 2018-12-27 built on MACHINE
Repository revision: ee7514b91beb254a7dc62f618046d34036555cea
Repository branch: master
Windowing system distributor 'Microsoft Corp.', version 10.0.17134
System Description: Microsoft Windows 10 Pro (v10.0.1803.17134.523)

Recent messages:
For information about GNU Emacs and the GNU system, type C-h C-a.

Configured using:
 'configure --config-cache --with-modules --without-pop 'CFLAGS=-O0
 -ggdb3''

Configured features:
XPM JPEG TIFF GIF PNG RSVG SOUND DBUS NOTIFY W32NOTIFY ACL GNUTLS
LIBXML2 ZLIB TOOLKIT_SCROLL_BARS MODULES THREADS JSON LCMS2 GMP

Important settings:
  value of $EMACSLOADPATH: c:\emacs-lisp;
  value of $LANG: ENG
  locale-coding-system: cp1252

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
  transient-mark-mode: t

Load-path shadows:
None found.

Features:
(shadow sort mail-extr emacsbug message rmc puny seq byte-opt gv
bytecomp byte-compile cconv dired dired-loaddefs format-spec rfc822 mml
easymenu mml-sec password-cache epa derived epg epg-config gnus-util
rmail rmail-loaddefs time-date 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 elec-pair
mule-util tooltip eldoc electric uniquify ediff-hook vc-hooks
lisp-float-type mwheel dos-w32 ls-lisp disp-table term/w32-win w32-win
w32-vars term/common-win tool-bar dnd fontset image regexp-opt fringe
tabulated-list replace newcomment text-mode elisp-mode lisp-mode
prog-mode register page menu-bar rfn-eshadow isearch timer select
scroll-bar mouse jit-lock font-lock syntax facemenu font-core
term/tty-colors frame 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 minibuffer cl-preloaded nadvice loaddefs
button faces cus-face macroexp files text-properties overlay sha1 md5
base64 format env code-pages mule custom widget hashtable-print-readable
backquote threads w32notify dbusbind w32 lcms2 multi-tty
make-network-process emacs)

Memory information:
((conses 16 99293 11660)
 (symbols 48 20104 1)
 (strings 32 29966 1902)
 (string-bytes 1 774918)
 (vectors 16 15098)
 (vector-slots 8 506058 15028)
 (floats 8 53 221)
 (intervals 56 245 20)
 (buffers 992 11))

Message #8 received at 34059 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Richard Copley <rcopley <at> gmail.com>
Cc: 34059 <at> debbugs.gnu.org
Subject: Re: bug#34059: 27.0.50; Emacs hangs on typing quit (MS-Windows)
Date: Sun, 13 Jan 2019 17:17:28 +0200

> From: Richard Copley <rcopley <at> gmail.com>
> Date: Sun, 13 Jan 2019 13:04:05 +0000
> 
> Emacs sometimes hangs on typing quit, on MS-Windows.

Thanks, but if you can, please provide more details about what was
Emacs doing when this happens.

> (See also <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25279#69>.)

That one was fixed, AFAIU.

Message #11 received at 34059 <at> debbugs.gnu.org (full text, mbox):

From: Richard Copley <rcopley <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 34059 <at> debbugs.gnu.org
Subject: Re: bug#34059: 27.0.50; Emacs hangs on typing quit (MS-Windows)
Date: Sun, 13 Jan 2019 16:00:23 +0000

On Sun, 13 Jan 2019 at 15:17, Eli Zaretskii <eliz <at> gnu.org> wrote:
>
> > From: Richard Copley <rcopley <at> gmail.com>
> > Date: Sun, 13 Jan 2019 13:04:05 +0000
> >
> > Emacs sometimes hangs on typing quit, on MS-Windows.
>
> Thanks, but if you can, please provide more details about what was
> Emacs doing when this happens.

I'm not sure exactly, sorry. I would have been reading console output
from a process in a compilation-mode buffer, and using git via magit,
around the time.

> > (See also <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25279#69>.)
>
> That one was fixed, AFAIU.

The message says "I'll send another report if and when I catch another hang".

Message #14 received at 34059 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Richard Copley <rcopley <at> gmail.com>
Cc: 34059 <at> debbugs.gnu.org
Subject: Re: bug#34059: 27.0.50; Emacs hangs on typing quit (MS-Windows)
Date: Mon, 14 Jan 2019 17:40:08 +0200

> From: Richard Copley <rcopley <at> gmail.com>
> Date: Sun, 13 Jan 2019 16:00:23 +0000
> Cc: 34059 <at> debbugs.gnu.org
> 
> On Sun, 13 Jan 2019 at 15:17, Eli Zaretskii <eliz <at> gnu.org> wrote:
> >
> > > From: Richard Copley <rcopley <at> gmail.com>
> > > Date: Sun, 13 Jan 2019 13:04:05 +0000
> > >
> > > Emacs sometimes hangs on typing quit, on MS-Windows.
> >
> > Thanks, but if you can, please provide more details about what was
> > Emacs doing when this happens.
> 
> I'm not sure exactly, sorry. I would have been reading console output
> from a process in a compilation-mode buffer, and using git via magit,
> around the time.

Any chance you could recollect why did you type C-g while at that?

> > > (See also <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25279#69>.)
> >
> > That one was fixed, AFAIU.
> 
> The message says "I'll send another report if and when I catch another hang".

I've found one, possibly two more places where we could QUIT while
holding a critical section.  I cannot know if they were part of your
hang, but I went ahead and fixed them on the emacs-26 branch.  Let's
see if they stop these hangs from happening.

Thanks.

Message #17 received at 34059 <at> debbugs.gnu.org (full text, mbox):

From: Richard Copley <rcopley <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 34059 <at> debbugs.gnu.org
Subject: Re: bug#34059: 27.0.50; Emacs hangs on typing quit (MS-Windows)
Date: Mon, 14 Jan 2019 19:39:07 +0000

[Message part 1 (text/plain, inline)]

On Mon, 14 Jan 2019, 15:40 Eli Zaretskii <eliz <at> gnu.org wrote:

> > From: Richard Copley <rcopley <at> gmail.com>
> > Date: Sun, 13 Jan 2019 16:00:23 +0000
> > Cc: 34059 <at> debbugs.gnu.org
> >
> > On Sun, 13 Jan 2019 at 15:17, Eli Zaretskii <eliz <at> gnu.org> wrote:
> > >
> > > > From: Richard Copley <rcopley <at> gmail.com>
> > > > Date: Sun, 13 Jan 2019 13:04:05 +0000
> > > >
> > > > Emacs sometimes hangs on typing quit, on MS-Windows.
> > >
> > > Thanks, but if you can, please provide more details about what was
> > > Emacs doing when this happens.
> >
> > I'm not sure exactly, sorry. I would have been reading console output
> > from a process in a compilation-mode buffer, and using git via magit,
> > around the time.
>
> Any chance you could recollect why did you type C-g while at that?
>

Not really. I had invoked M-x recompile, and didn't immediately see
results in the compilation-mode buffer. That's not a compelling reason
to type C-g so I suppose I had done something else too.

The file I was editing/compiling wasn't saved (I recovered it from a
stale autosave later). I don't remember whether I saw the "Save file
%s? (...)" question, nor whether I had answered it if so. (I mention
this in case it's a useful clue. Probably not.)

> The message says "I'll send another report if and when I catch another
hang".

>
> I've found one, possibly two more places where we could QUIT while
> holding a critical section.  I cannot know if they were part of your
> hang, but I went ahead and fixed them on the emacs-26 branch.  Let's
> see if they stop these hangs from happening.
>

Great, thanks. Let's see.

[Message part 2 (text/html, inline)]

Message #20 received at 34059 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefan <at> marxist.se>
To: Richard Copley <rcopley <at> gmail.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 34059 <at> debbugs.gnu.org
Subject: Re: bug#34059: 27.0.50; Emacs hangs on typing quit (MS-Windows)
Date: Thu, 23 Jan 2020 15:35:34 +0100

Hi Richard,

Richard Copley <rcopley <at> gmail.com> writes:

> On Mon, 14 Jan 2019, 15:40 Eli Zaretskii <eliz <at> gnu.org wrote:
>
>  > From: Richard Copley <rcopley <at> gmail.com>
>  > Date: Sun, 13 Jan 2019 16:00:23 +0000
>  > Cc: 34059 <at> debbugs.gnu.org
>  > 
>  > On Sun, 13 Jan 2019 at 15:17, Eli Zaretskii <eliz <at> gnu.org> wrote:
>  > >
>  > > > From: Richard Copley <rcopley <at> gmail.com>
>  > > > Date: Sun, 13 Jan 2019 13:04:05 +0000
>  > > >
>  > > > Emacs sometimes hangs on typing quit, on MS-Windows.
>  > >
>  > > Thanks, but if you can, please provide more details about what was
>  > > Emacs doing when this happens.
>  > 
>  > I'm not sure exactly, sorry. I would have been reading console output
>  > from a process in a compilation-mode buffer, and using git via magit,
>  > around the time.
>
>  Any chance you could recollect why did you type C-g while at that?
>
> Not really. I had invoked M-x recompile, and didn't immediately see
> results in the compilation-mode buffer. That's not a compelling reason
> to type C-g so I suppose I had done something else too.
>
> The file I was editing/compiling wasn't saved (I recovered it from a
> stale autosave later). I don't remember whether I saw the "Save file
> %s? (...)" question, nor whether I had answered it if so. (I mention
> this in case it's a useful clue. Probably not.)
>
>> The message says "I'll send another report if and when I catch another hang".
>
>  I've found one, possibly two more places where we could QUIT while
>  holding a critical section.  I cannot know if they were part of your
>  hang, but I went ahead and fixed them on the emacs-26 branch.  Let's
>  see if they stop these hangs from happening.
>
> Great, thanks. Let's see.

That was one year ago.  Are you still seeing this on the most recent
version of Emacs?

Best regards,
Stefan Kangas

Message #25 received at 34059-done <at> debbugs.gnu.org (full text, mbox):

From: Richard Copley <rcopley <at> gmail.com>
To: Stefan Kangas <stefan <at> marxist.se>
Cc: 34059-done <at> debbugs.gnu.org
Subject: Re: bug#34059: 27.0.50; Emacs hangs on typing quit (MS-Windows)
Date: Thu, 23 Jan 2020 19:46:47 +0000

Closing.

On Thu, 23 Jan 2020 at 19:44, Richard Copley <rcopley <at> gmail.com> wrote:
>
> On Thu, 23 Jan 2020 at 14:35, Stefan Kangas <stefan <at> marxist.se> wrote:
>
> > That was one year ago.  Are you still seeing this on the most recent
> > version of Emacs?
>
> No, seems fixed. Thanks.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.