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

[Noam Postavsky]

Boruch Baum <boruch_baum@gmx.com> writes:

> Today, with no javascript mode buffer open, when running M-x
> list-timers, two javascript-related timers appear:
>
>    *       0.50        t jit-lock-context-fontify

I don't think this one is javascript-related.

>    *      30.00        t js-gc
>
> So, it looks like those timers aren't being properly killed. I have no
> idea when I have ever opened a buffer in some form of javascript mode;
> my emacs-uptime is 20+ days.

js.el has at top-level:

    (run-with-idle-timer 30 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.  Do you see any
problems coming from the existence of this timer?