Appreciate the prompt and detailed response. Your project is rather basic, and the JDT classloaders do look like the most likely culprits, can't point to anything else that would lock the resources.
There is a recently revived bug over at Eclipse on this same issue, which you can find here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=406170
We may pick up a fix in the next release of Eclipse if the JDT team fixes the issue or be able to patch the plugins responsible if not too dangerous. We'll keep our eyes on this bug to see how it progresses over the next few weeks. Since you can replicate the problem, your team could probably contribute invaluable debugging information as well.
The files are possibly being locked by the Java tools (JDT) classloader, or other loaders that are accessing the libraries to provide code assistance, analytics, etc. Unfortunately hard to say without further analysis.
We have a few questions:
1) What OS is this, I'm assuming it's Windows? What version?
2) How are you deploying the project, and what server are you deploying to?
2.a) Are you using a custom deployment which results in the server using the same resources that are in the workspace? In that case, the server could be locking the files too. Do you find that the files are normally locked only after you deploy?
3) Does the 3rd party tool report what process is locking the files?
4) Could you give us the crash log when ME crashes as a result of releasing the log?
(Consider writing to firstname.lastname@example.org with a link to this post)
5) Can you tell us what sort of project this is? i.e. Dynamic web project + Spring / JSF, etc? You could also send us all the files in the ".settings" folder, we could figure it out from there too.
Hope we'll be be able to figure this out with your support Thank you for reporting the problem and the details.
With MyEclipse 2015 we moved to a Tern based inference engine from the older JSDT engine.
Beyond MyEclipse 2015 CI 12 and in MyEclipse 2016 / 2017, JS performance is far improved out of the box so no additional tweaking should be required.
If you still experience problems, you can change some settings or turn off the support entirely – see https://www.genuitec.com/forums/topic/troubleshooting-performance-issues-in-myeclipse-2015/ for details
Apologies for the broken link, please see the updated answer with the correct link above: https://www.genuitec.com/forums/topic/troubleshooting-performance-issues-in-myeclipse-2015/
With recent versions of 2015 and 2016, you should not really be having any performance issues out of the box. If you have followed the steps in the above link and still experience problems, please post on our forums so we can follow-up in more detail.
We’ve just implemented an open issue tracker here: https://www.genuitec.com/issue-tracker/. As of this date, it is only available for our free Darkest Dark plugin, but we’ll be expanding it to other products soon. As for posting issues/enhancements, those can be done right now on the forums here: https://www.genuitec.com/forums/topics/webclipse/
Thanks for the suggestion -- we'll definitely investigate to see what makes sense.
You can let us know about issues in our forums:
And as you've found, our user voice forum is a great place to suggest improvements.