bug#40771: 26.1: javascript-mode timers persist after closing mode buffers

[Boruch Baum]

On 2020-04-27 10:35, Noam Postavsky wrote:
> Boruch Baum <boruch_baum@gmx.com> writes:
> >    *       0.50        t jit-lock-context-fontify
>
> I don't think this one is javascript-related.

Oops. You're quite right on that one.

> >    *      30.00        t js-gc
> It's a global timer which isn't connected to any particular buffer.  I'm
> not sure why you think the timer should be killed.

It's associated with file js.el "Major mode for editing JavaScript", so
if no buffer is using that major mode, or more charitably if no buffer
is editing javascript, then the timer is cruft.

>  Do you see any problems coming from the existence of this timer?

I'm not sure. The immediate reason I bothered to perform M-x list-timers
was trouble I had killing the scrolling ticker of newsticker.el. The
reason I killed the two timers was to see if doing so would stop my
emacsclient process from intermittently freezing. I've been having a
recurring problem with that, on average once every few weeks: the server
process remains functional, so I don't lose any work or data, but I need
to kill the emacsclient process and re-connect to the server.

In any event, the metric shouldn't be whether anyone "sees any problems
coming from its existence", the metric should be whether its continued
existence is good software engineering practice. Likewise for Dmitry
Gutov's suggestion to remove code associated with MozRepl.

--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1  7286 0036 9E45 1595 8BC0