Subject: bug#16387: 24.3.50; unquittable infloop

From: Stefan Kangas <[email-masked]>
Date: Wed, 12 Aug 2020 15:23:28 -0700

Richard Stallman <[email-masked]> writes:

> M-x grep put me in a loop I could not quit out of.
> Here's the backtrace after C-g C-g put me into GDB.
> Grep had already terminated, but Emacs had not exited the loop
> even a minute later.
>
> It happened twice today.  One time, the current buffer was in Mail mode,
> and maybe that was true both times.
>
>
> #0  0x76a4d3c4 in kill () from /lib/libc.so.6
> #1  0x00657004 in sys_suspend () at sysdep.c:450
> #2  0x0063fcf8 in handle_interrupt (in_signal_handler=true) at keyboard.c:10318
> #3  0x0063fb18 in handle_interrupt_signal (sig=2) at keyboard.c:10259
> #4  0x006599b0 in deliver_process_signal (sig=2,
>     handler=0x63fa78 <handle_interrupt_signal>) at sysdep.c:1568
> #5  0x0063fb74 in deliver_interrupt_signal (sig=2) at keyboard.c:10266
> #6  <signal handler called>
> #7  0x00000000 in ?? ()
> #8  0x00000000 in ?? ()
>
> Lisp Backtrace:
> "get-text-property" (0x7fff09e8)
> "font-lock-extend-jit-lock-region-after-change" (0x7fff0dbc)
> "run-hook-with-args" (0x7fff0db8)
> "jit-lock-after-change" (0x7fff1144)
> "replace-match" (0x7fff1348)
> "grep-filter" (0x7fff1698)
> "run-hooks" (0x7fff1710)
> "compilation-filter" (0x7fff19dc)

This was reported 6.5 years ago.  Are you still seeing this?

Best regards,
Stefan Kangas