-
-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fail start mode with "Error running timer" on Emacs 31.0.50 #603
Comments
Hi! Are you sure reproducing this bug doesn't require some specific code to be present in the buffer? |
Yes, you're right. Now I see that it fails only for some code. Here is a minimal js that reproduces this case: document.addEventListener('DOMContentLoaded', function() {
var id = null;
}); |
Thank you. Any chance you're using an older version of js2-mode, maybe? I'm testing with Emacs 31.0.50 built from the current master and the latest js2-mode, and I'm not seeing any error with these buffer contents. |
No, it is an actual MELPA version: So, the actual workaround for me is: (setq native-comp-jit-compilation-deny-list '("js2-mode")) UPD: Not fully relevant to (setq native-comp-jit-compilation-deny-list
'("js2-mode" "rjsx-mode")) |
All right, that makes sense. I also remember a couple of bugs in the similar vein that only happen with native compilation. Problem is, each has to be reported and fixed separately. And like the last time, it doesn't reproduce on my machine if I just reconfigure So if you could do a |
You can try deleting the existing native-compilation cache, BTW. IIRC this helped in some instance of this problem in the past. |
GNU Emacs 31.0.50
(build frommaster
, commit:d50c82f3e98e5418e5a42b48162bc26028309b89
)Steps to reproduce:
M-x js2-mode
Message:
Error running timer ‘js2-mode-idle-reparse’: (args-out-of-range #s(js2-keyword-node 44 253 5 nil nil) 6)
Full trace with
M-x toggle-debug-on-error
:The text was updated successfully, but these errors were encountered: