Endless diagnostic publishing when validation is disabled

[IdanHo]

After updating from version 0.18.2 (As part of the vscode-xml) extension the lemminx-linux binary is using 100% of my cpu. (Same behaviour with 0.18.3, 0.18.4, 0.19.0). I don't have a specific xml file to point to, since it does so as soon as I open a container, without opening any XML files. I don't have debug symbols, but after attaching with GDB, these are the locations of all the threads:

[angelozerr]

You mean that you don't open some XML file? I have no idea why you have this problem.

@rgrunber @fbricon have you some idea?

[IdanHo]

I don't open any XML file. note that I'm running on the Remote - Containers extension connected to a CentOS 7 container. and that it happens on both Linux and WSL

[IdanHo]

Ah, after restarting the container it didn't happen, so it's likely left over from when I did open an XML file, but I created this example file:

<?xml version="1.0" encoding="UTF-8"?>
<test>
</test>

and as soon as I opened it, it started happening.

[angelozerr]

And do you benefit with syntax validation?

[IdanHo]

I have this "xml.validation.enabled": false set if that's what you mean.

[angelozerr]

Could you enable xml trace https://github.com/redhat-developer/vscode-xml/blob/master/docs/Troubleshooting.md#no-support-on-xml-file and share your trace please

I have this "xml.validation.enabled": false set if that's what you mean.

Ok but have you some XML features like completion, hover, linked editing range, etc?

[IdanHo]

Ok but have you some XML features like completion, hover, linked editing range, etc?

All of them seem to be loading forever.

[IdanHo]

Could you enable xml trace https://github.com/redhat-developer/vscode-xml/blob/master/docs/Troubleshooting.md#no-support-on-xml-file and share your trace please

I'm just seeing this on repeat:

[Trace - 10:04:25 AM] Received notification 'textDocument/publishDiagnostics'.
Params: {
    "uri": "file:///workspaces/repo/test.xml",
    "diagnostics": []
}

(As in, it's receiving this notification a bunch of times every second)

[angelozerr]

I don't understand, if you set "xml.validation.enabled": false you should not have 'textDocument/publishDiagnostics'.

What is your trace when the language server is started?

[angelozerr]

The impression that I have is that the language server started and (perhaps) the settings is not valid and doesn't take care of your enabled validation settings.

The server crashes and restart again. Not sure with that but it's an idea.

[IdanHo]

Attached is the startup trace
trace.log

[fbricon]

@IdanHo do you use a specific container? Can you install a JDK in the container and point xml.java.home to it?

[angelozerr]

@IdanHo thanks so much with your trace, I can reproduce the problem and I know how to fix it.

For the moment to avoid having this trouble, please set "xml.validation.enabled": true

[IdanHo]

For the moment to avoid having this trouble, please set "xml.validation.enabled": true

Thanks!

[fbricon]

@IdanHo vscode-xml 0.19.1, which includes a fix for this issue, has been released to the VS Code Marketplace

[IdanHo]

@IdanHo vscode-xml 0.19.1, which includes a fix for this issue, has been released to the VS Code Marketplace

That update indeed fixed the issue, thank you!