GNU bug report logs - #30112
27.0.50; bibtex-mode timer and JIT font lock errors

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 30112 in the body.
You can then email your comments to 30112 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: "Basil L. Contovounesios" <contovob <at> tcd.ie>
To: bug-gnu-emacs <at> gnu.org
Subject: 27.0.50; bibtex-mode timer and redisplay errors
Date: Sun, 14 Jan 2018 15:27:18 +0000

Steps to reproduce:

1. emacs -Q
2. C-x h DEL
3. C-h e
4. M-: (setq bibtex-parse-keys-timeout 4) RET
   [ or some other convenient value ]
5. M-x bibtex-mode RET
6. C-o
   [ this (IMO) incorrectly inserts a large fill-prefix, but that's a
     separate bug ]

After a few seconds of idle time, the following error is logged to
*Messages*:

  Error during redisplay: (jit-lock-function 1) signaled
  (args-out-of-range #<buffer *scratch*> 0 1)

After bibtex-parse-keys-timeout seconds of idle time, another error
appears:

  Error running timer ‘bibtex-parse-buffers-stealthily’:
  (wrong-type-argument number-or-marker-p nil)

Enabling debug on error does not provide much more context:

  Debugger entered--Lisp error:
      (wrong-type-argument number-or-marker-p nil)
    bibtex-parse-keys(t)
    bibtex-parse-buffers-stealthily()
    apply(bibtex-parse-buffers-stealthily nil)
    timer-event-handler
      ([t 0 4 0 t bibtex-parse-buffers-stealthily nil idle 0])

Note that step (6) is only needed to trigger the redisplay error; the
bibtex parse timer fails even when the buffer is empty.

-- 
Basil

In GNU Emacs 27.0.50 (build 15, x86_64-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
 of 2018-01-11 built on thunk
Repository revision: e911587fb61bbc7f4be41e0a044cb6dee8f9e615
Windowing system distributor 'The X.Org Foundation', version 11.0.11905000
System Description: Debian GNU/Linux testing (buster)

Configured using:
 'configure --config-cache --prefix=/home/blc/.local --with-mailutils
 --with-x-toolkit=lucid --with-modules --with-file-notification=yes
 --with-x 'CFLAGS=-flto -fomit-frame-pointer -march=native -maes -mavx
 -mcrc32 -mf16c -mfpmath=sse -mfsgsbase -mfxsr -minline-all-stringops
 -mmmx -mpclmul -mpopcnt -msahf -msse4.2 -mxsave -mxsaveopt -mvzeroupper
 -O3 -pipe' LDFLAGS=-flto'

Configured features:
XAW3D XPM JPEG TIFF GIF PNG RSVG IMAGEMAGICK SOUND GPM DBUS GSETTINGS
NOTIFY ACL LIBSELINUX GNUTLS LIBXML2 FREETYPE M17N_FLT LIBOTF XFT ZLIB
TOOLKIT_SCROLL_BARS LUCID X11 MODULES LIBSYSTEMD JSON LCMS2

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: "Basil L. Contovounesios" <contovob <at> tcd.ie>
Cc: 30112 <at> debbugs.gnu.org
Subject: Re: bug#30112: 27.0.50; bibtex-mode timer and redisplay errors
Date: Sun, 14 Jan 2018 18:05:14 +0200

> From: "Basil L. Contovounesios" <contovob <at> tcd.ie>
> Date: Sun, 14 Jan 2018 15:27:18 +0000
> 
>   Error during redisplay: (jit-lock-function 1) signaled
>   (args-out-of-range #<buffer *scratch*> 0 1)
> [...]
> 
> Note that step (6) is only needed to trigger the redisplay error

It's not a redisplay error, it's a JIT Font lock error.  Redisplay
calls JIT lock as part of redisplaying the window, so it catches the
error and reports it.

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

From: "Basil L. Contovounesios" <contovob <at> tcd.ie>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 30112 <at> debbugs.gnu.org
Subject: Re: bug#30112: 27.0.50; bibtex-mode timer and redisplay errors
Date: Sun, 14 Jan 2018 16:54:50 +0000

Eli Zaretskii <eliz <at> gnu.org> writes:

> It's not a redisplay error, it's a JIT Font lock error.  Redisplay
> calls JIT lock as part of redisplaying the window, so it catches the
> error and reports it.

Right, sorry - that was a thinko on my part.

Is it possible to reword debbugs subject lines?

-- 
Basil

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: "Basil L. Contovounesios" <contovob <at> tcd.ie>
Cc: 30112 <at> debbugs.gnu.org
Subject: Re: bug#30112: 27.0.50; bibtex-mode timer and redisplay errors
Date: Sun, 14 Jan 2018 19:22:54 +0200

> From: "Basil L. Contovounesios" <contovob <at> tcd.ie>
> Cc: <30112 <at> debbugs.gnu.org>
> Date: Sun, 14 Jan 2018 16:54:50 +0000
> 
> Is it possible to reword debbugs subject lines?

There's the "retitle" command, see admin/notes/bugtracker for the
details.

Thanks.

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

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: "Basil L. Contovounesios" <contovob <at> tcd.ie>
Cc: 30112 <at> debbugs.gnu.org
Subject: Re: bug#30112: 27.0.50; bibtex-mode timer and redisplay errors
Date: Sun, 17 Nov 2019 09:16:15 +0100

"Basil L. Contovounesios" <contovob <at> tcd.ie> writes:

> Enabling debug on error does not provide much more context:
>
>   Debugger entered--Lisp error:
>       (wrong-type-argument number-or-marker-p nil)
>     bibtex-parse-keys(t)
>     bibtex-parse-buffers-stealthily()
>     apply(bibtex-parse-buffers-stealthily nil)
>     timer-event-handler
>       ([t 0 4 0 t bibtex-parse-buffers-stealthily nil idle 0])

I've now added a sanity check to bibtex-parse-keys to abort in these
situations to Emacs 27.

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

Previous Next

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