GNU bug report logs - #39967
27.0.90; how to debug point moving erratically?

Previous Next

Package: emacs;

Reported by: William Rankin <william <at> bydasein.com>

Date: Sat, 7 Mar 2020 04:07:02 UTC

Severity: normal

Tags: moreinfo

Found in version 27.0.90

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: William Rankin <william <at> bydasein.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 39967 <at> debbugs.gnu.org
Subject: bug#39967: 27.0.90; how to debug point moving erratically?
Date: Sat, 7 Mar 2020 23:47:24 +1000
> On 7 Mar 2020, at 11:06 pm, Eli Zaretskii <eliz <at> gnu.org> wrote:
> 
> If this happens when Emacs is idle, the first suspect is some idle
> timer you have running.  The variable timer-idle-list holds the list
> of the active idle timers, so look there for some hints.

This is what made me suspect jit-lock, because of the 5 sec idle timer 
followed by jumping at 0.5 secs intervals.

Here's my timer list:

           0.37     0.01 blink-cursor-timer-function
           6.59        - undo-auto--boundary-timer
          47.03     1.00 display-time-event-handler
   *       0.00        t show-paren-function
   *       0.50        t #f(compiled-function () #<bytecode 0x41903951> [jit-lock--antiblink-grace-timer jit-lock-context-fontify])
   *       0.50  :repeat blink-cursor-start
   *       1.00        t which-key--update
   *       5.00        t jit-lock-stealth-fontify

Could the sporadic nature hint at the byte-compiled function that calls 
jit-lock-context-fontify? (Also I see jit-lock-antiblink-grace is new 
in 27.)

Of course there's also which-key, so I've turned that off for the time
being.





This bug report was last modified 3 years and 101 days ago.

Previous Next


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