[4.35] On startup Java editor shows error annotations on valid code that don't always disappear

[Phillipus]

This is transferred from eclipse-jdt/eclipse.jdt.ui#2069

Eclipse 4.35 RC2
Java Temurin 21 SDK
Reproduced on Windows 11 and Mac Sequoia (not tested on Linux)

1. Download Eclipse 4.35 SDK from https://download.eclipse.org/eclipse/downloads/
2. Launch Eclipse with a fresh workspace
3. Create a sample plug-in project "Hello, World Command"
4. Open the file SampleHandler.java in the editor
5. Now close Eclipse and re-open Eclipse a few times.
6. Upon opening Eclipse I get red problem markers in the file. Many times these problem markers do not clear.

Edit - the first time re-opening Eclipse the red markers will disappear but after closing and re-opening thereafter the red markers remain.

A workaround is to add some text to the file such as a space and then undo.

This does not happen in Eclipse 4.34.

[Phillipus]

Comment from eclipse-jdt/eclipse.jdt.ui#2069

Switching PDE.ui to I20250106-1800 fixes the issue.
Updating to the commit 7e45ebb breaks. So it is a regression from #1552.

[iloveeclipse]

I was able to reproduce it easily following the steps in the bug on Linux, so it is not platform dependent.

[laeubi]

Sorry we won't do any fixing here.

See

• JDT calls PDE Classpath on startup with open Editor hindering the UI to show up #1481 (comment)

so if anyone is interested, please fix the issues in JDT / Platform and the problem will go away, there is nothing PDE can do.

[merks]

I've been seeing this as well on and off too. 😢

This is one of those bouncing issues where one seems to be damned if you do and damned if you don't, so I can empathize with not wanting to keep this bouncing this back to the previous poor state. Computing a classpath via some computation that may take minutes on the UI thread really needs to be avoided at the source. But the source seems not to want to do this.

In any case, one would hope and expect that when the job finishes computing the classpath that the editor's state would updated. Is there some notification or interaction missing? That would be the direction on which to focus I think, but I don't know who or where that should happen.

[Phillipus]

So, should I transfer this issue somewhere else? (Don't shoot the messenger)

[laeubi]

In any case, one would hope and expect that when the job finishes computing the classpath that the editor's state would updated. Is there some notification or interaction missing?

That's possible, but still something not PDE can fix ..

So, should I transfer this issue somewhere else? (Don't shoot the messenger)

As said there are already issues created:

• [performance] PackageFragmentRoot.getRawClasspathEntry() has bad impact on startup performance eclipse-jdt/eclipse.jdt.core#3468
• [performance] CloseUnrelatedProjectsAction.buildConnectedComponents(IProject[]) blocks UI startup eclipse-platform/eclipse.platform.ui#2636
• [performance] JDT initialization blocks IDE startup eclipse-jdt/eclipse.jdt.ui#1860

one would maybe open another one for the reasons @merks has mentioned.