-
Notifications
You must be signed in to change notification settings - Fork 414
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
Server stops when idling after failing to track VS Code's PID #815
Comments
try to disable every extension but vscode-java, clean the workspace and see what happens |
@fbricon Hi and thank you for answering. I've done both things with the same result. My settings.json in case needed.
|
please resend your Language Support Java Output, when all extensions are disabled |
the STS extensions are still active apparently |
I uninstalled the other extensions and removed its folders from |
@snjeza any idea? |
@adriantomas could try the following:
or remove and reinstall the RedHat Java LS extension. |
Done above steps. This is the output of removing those directories: Also reinstalled VSCode removing related directories at |
@adriantomas could you send the output of the following command:
|
Typed above commands after the Java Support for Java server crashed. |
@adriantomas could you try the following:
You can also check the following VS Code Java - https://drive.google.com/open?id=1m91etQ-3JugTjBYQbptWGsw3Nq89-GvI. It includes eclipse-jdtls/eclipse.jdt.ls#946 |
This is the output of the commands. Sorry for misunderstanding them at first. Tasklist output in E drive.txt Then I installed the 0.41.0 version of vscode-java and cleant the java language server workspace. This is the output of the Language Support for Java extension and the output of the above commands with this version. Language Support Java Output (0.41.0).txt |
@adriantomas Could you, please, try the following version - https://drive.google.com/open?id=1yIYJyeDbvshorQgH7OVYt5_-m8CDR5PQ ? |
Just for cleaning things up I performed a fresh vscode installation again, deleting The Language Support for Java server is actually working and has not crashed a single time Language Support Java Output (0.41.1).txt I would like to know how this ended up working. Thank you a lot @snjeza @fbricon |
I have tried to test your the tasklist and findstr command. You can ignore it or try the following build - https://drive.google.com/open?id=1mnSeXB5JBVNhWbC9Osmx_lzzk6DEQBpe .
It seems that you have a corrupted tasklist or findstr command.
eclipse-jdtls/eclipse.jdt.ls#946 fixes the issue. The 0.41.1 and 0.41.2 versions includes it. |
So I installed the 0.41.2 version and it worked. Then rolled back to the standard 0.40.0 and it's working! I'm confused but happy is finally running. |
I suppose that you had a corrupted tasklist or findstr command and removed it. |
A couple things to notice that maybe caused the error and what I did. These are some possible workarounds for users that have the same problem I had:
I don't know if this means something to you @snjeza |
@adriantomas Thanks, that is helpful. |
Not work, maybe new vscode cause this. |
@di3663 please send your Language Support Java Output, |
@pehalo Does this issue still happen? |
It just happened, but the automatic restart was successful. My computer's memory is full during the reboot process.sorry! I just checked it. It failed to restart |
@pehalo Could you help invoke the "Java: Clean workspace ..." command to see whether the issue persist |
@yaohaizh After running the "Java: Clean workspace" command, I found some other problems. |
A GC is performed every 10sec, to prevent a file handle leak on Windows |
Receiving the following error when opening a Spring Boot Maven project folder:
The Language Support for Java server crashed 5 times in the last 3 minutes. The server will not be restarted.
Environment
Steps To Reproduce
Java Language Server log.txt
Language Support Java Output.txt
Additional Informations
I have the Windows system AV. Also followed the steps here and in many other related issues. I've cleaned the language server workspace.
The text was updated successfully, but these errors were encountered: