Replies: 1 comment
-
|
I did this today:
Back up and things seems to be working. At least JDTLS isn't crashing for me all the time now, with just a single eclipse workspace imported. Time will show how JDTLS and lsp-mode handles getting more eclipse workspaces in the list (most of my projects are maven multi module java projects, where the top pom directory also serves as an eclipse workspace). |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Platform emacs 30.1, debian 13.4 "trixie", amd64, lsp-mode 20260424.1524 (melpa)
Need help debugging JDTLS crashes.
JDTLS keeps crashing for me with the following error messages in the minibuffer
When I check the stderr buffer as suggested, all the stderr buffer contains is:
The FAQ How do I troubleshoot "Server FOO-LS:pid exited with status signal. Do you want to restart it? (y or n)"? says to then check the
*lsp-log*buffer, but there isn't much of interest their either: https://gist.github.com/steinarb/d2f12c882d21d712beacfd6d95920a07(or rather: nothing in lsp-log tells my anything I'm able to make use of to debug this)
My
.emacssetup for lsp-mode for java combined with treesitter for java is here:More information: I visit a lot of java projects in different workspaces, some of which are quite large (local clones of various open source projects) and I think my setup uses only a single workspace in JDT.LS..? So maybe the workspace has gotten too large for JDTLS...? (just guessing here...)
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions