We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Sometimes when you exit VS Code while vscode-xml was running, there is a Java process called XMLServerLauncher that remains.
XMLServerLauncher
If that process remains, and vscode-xml is started up again, there is an error about the XML language server crashing 5 times in the last 3 minutes.
To fix this problem vscode-xml should call stop() on the languageClient in the deactivate() method, which is what vscode-java does: https://github.com/redhat-developer/vscode-java/blob/c7afc32bde70f5afc292966c1311ec4dd1bfe9b5/src/extension.ts#L384-L387
stop()
deactivate()
to ensure that the process is terminated when the extension is deactivated.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Sometimes when you exit VS Code while vscode-xml was running, there is a Java process called
XMLServerLauncher
that remains.If that process remains, and vscode-xml is started up again, there is an error about the XML language server crashing 5 times in the last 3 minutes.
To fix this problem vscode-xml should call
stop()
on the languageClient in thedeactivate()
method, which is what vscode-java does:https://github.com/redhat-developer/vscode-java/blob/c7afc32bde70f5afc292966c1311ec4dd1bfe9b5/src/extension.ts#L384-L387
to ensure that the process is terminated when the extension is deactivated.
The text was updated successfully, but these errors were encountered: