You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a Quarkus extension project which seems to be the only project this is (and has ever) happening with.
The language server never fully initializes.
Almost everything works. What doesn't work:
Syntax highlighting on imports
Formatting, sort imports on save, other similar action
Ctrl + Click to jump to definition on non JRE methods (any external libraries)
👇 CLICK TO SEE SCREENSHOTS 👇
I tried to debug to the limits my (very limited) experience with Java/the JVM would allow
Investigated with VisualVM -- thread dumps, profiling, and JFR.
Appears like the application + over half of it's threads are in a wait state
Here is the project source and a very lengthy JFR recording:
I have a Quarkus extension project which seems to be the only project this is (and has ever) happening with.
The language server never fully initializes.
Almost everything works. What doesn't work:
👇 CLICK TO SEE SCREENSHOTS 👇
I tried to debug to the limits my (very limited) experience with Java/the JVM would allow
Investigated with VisualVM -- thread dumps, profiling, and JFR.
Appears like the application + over half of it's threads are in a wait state
Here is the project source and a very lengthy JFR recording:
NOTE: Also why in the JFR snapshot does the JDT server persistently send network requests to a local docker network URL?
Environment
Operating System:
JDK version:
Visual Studio Code version:
Java extension version:
v0.80.0
Steps To Reproduce
[Please attach a sample project reproducing the error]
Please attach logs
Additional Informations
Main thread just
waiting
indefinitely I think is what this is saying?From JFR snapshot, it seems to be stuck in a
wait
, here in the callstack:Also, for some reason there is a bunch of network activity to a local Docker network. What's going on with that?
The text was updated successfully, but these errors were encountered: