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
Hi ProuDog, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.
Here are some steps you can try when the Java extension “gets stuck”:
Check the Java Language Server logs for errors:
In VS Code, open the Output panel (View → Output).
Select Language Support for Java from the dropdown.
Look for repeated errors or stack traces.
Clean and restart the language server:
Run the Java: Clean the Java language server workspace command (⇧⌘P or Ctrl+Shift+P).
Reload the window (Developer: Reload Window).
Disable other extensions that may interfere (e.g., IntelliCode or code formatters), then reload.
Update to the latest Java extension pack (v0.45.0+), as many stability fixes land in patch releases.
If the issue persists, collect the language server logs and file a new issue including:
Full Error or Exception stack trace from the Output panel.
The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!
Thanks for the report. Based on the linked issue redhat-developer/vscode-java#4308, the root cause is a corrupted redhat.java (vscode-java) installation (missing config.ini), not an issue in vscode-java-test. The reporter already confirmed that switching to the vscode-java pre-release resolved the problem.
For a clean fix on the release channel, please follow the steps suggested in redhat-developer/vscode-java#4308 (close VS Code, delete the java extensions under %USERPROFILE%\.vscode\extensions and %APPDATA%\Code\CachedExtensions\, then reinstall vscode-java 1.51.0).
Closing here since this is not actionable in vscode-java-test. Please continue the discussion in the upstream issue if the problem persists.
Activity
github-actions commentedon Jan 15, 2026
Hi ProuDog, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.
Here are some steps you can try when the Java extension “gets stuck”:
Check the Java Language Server logs for errors:
Clean and restart the language server:
Disable other extensions that may interfere (e.g., IntelliCode or code formatters), then reload.
Update to the latest Java extension pack (v0.45.0+), as many stability fixes land in patch releases.
If the issue persists, collect the language server logs and file a new issue including:
Other references with low confidence
• Description: language support features (folding, hover) break with SIOOBE and then features get stuck
• No clear solution; suggestions included disabling IntelliCode and cleaning workspace
• URL: StringIndexOutOfBoundsException while computing hover and folding range redhat-developer/vscode-java#1644
The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!
wenytang-ms commentedon May 20, 2026
Thanks for the report. Based on the linked issue redhat-developer/vscode-java#4308, the root cause is a corrupted
redhat.java(vscode-java) installation (missingconfig.ini), not an issue in vscode-java-test. The reporter already confirmed that switching to the vscode-java pre-release resolved the problem.For a clean fix on the release channel, please follow the steps suggested in redhat-developer/vscode-java#4308 (close VS Code, delete the java extensions under
%USERPROFILE%\.vscode\extensionsand%APPDATA%\Code\CachedExtensions\, then reinstall vscode-java 1.51.0).Closing here since this is not actionable in vscode-java-test. Please continue the discussion in the upstream issue if the problem persists.