Eclipse XML Editor Running Too Wild

I installed Eclipse 2020-06 package for Java developers and added the Web Developer tools for better XML editing support. After a couple of minutes, XMLServerLauncher processes will start eating up my CPU cycles, even though I am not doing any heavy editing. After a while, Eclipse becomes unusable. I created a new workspace without copying any settings to make sure the issue was not caused by some legacy stuff in my projects or configuration.

Here you can see htop without any XML editing taking place (relevant processes shown):

I captured some memory and performance snapshots using yourkit, but I am not fit enough to identify the culprit in them quickly. I could upload them somewhere, if you think they would be useful in analyzing the problem.

Installation details attached (web developer plug-in version is 0.10.0.202006021616): eclipse_configuration.txt

Sorry, if this is the wrong place to report the bug, but a friendly person at @EclipseJavaIDE pointed me in this direction

[mickaelistria]

I don’t think there is anything Wild Web Developer can fix. The issue comes from m2e which embeds LemMinX-Maven. So I’ll close this issue.

eclipse/lemminx-maven#133 was fixed and lemminx-maven won’t spend CPU and network downloading index until a pom.xml file is open. However, it won’t reach m2e soon, you’ll probably have to wait about a month before we propagate this change available in m2e and Eclipse IDE.

We are limited to 8 GB networked home directories so a 2.5 GB index is a significant chunk of this.

I guess this case is not about Wild Web Developer, is it?

[joeshannon]

We have just been starting to experience what I believe to be the same issue after switching to 2020-06 (specifically Eclipse for RCP and RAP developers).

I haven’t fully investigated the triggers for this but as mentioned elsewhere it appears to happen possibly whenever an xml file is edited - the Eclipse projects themselves are not Maven projects (they are mostly Eclipse plugin projects).

The bigger problem for us is the amount of space that ~/.lemminx uses. We are limited to 8 GB networked home directories so a 2.5 GB index is a significant chunk of this.

I was just wondering if there are any known solutions/workarounds to this so far, for example disabling the index download or possibly changing its location?

Otherwise the only option I can see at the moment is symlinking that directory to somewhere e.g. under /tmp.