MacOS 14.3 M2: Temurin 17.0.10 has problem with starting an Eclipse RCP application

[ivy-lli]

Please provide a brief summary of the bug

Since the update to Temurin 17.0.10 (from Temurin 17.0.9), my started Eclipse RCP application shows only an empty screen.

Temurin 17.0.10:

Temurin 17.0.9:

Did you test with the latest update version?

Yes, I tested it with the latest Temurin 17.0.10 release (installed via homebrew).

Please provide steps to reproduce where possible

1. Install Eclipse RCP 2023-12 (4.30.0) https://www.eclipse.org/downloads/packages/release/2023-12/r/eclipse-ide-rcp-and-rap-developers
2. Create a new RCP application, done as described here: https://www.vogella.com/tutorials/EclipseRCP/article.html#generatetemplatewithcontent
3. Add Temurin 17.0.10 to Eclipse

• Open Preferences
• Java > Installed JREs
• Add...
• Select it
• Apply

4. Start the Eclipse application as described in the tutorial (Step 2)
   -> Empty application
5. Close the Eclipse application
6. Add Temurin 17.0.9 to Eclipse

• Same as step 3

7. Make sure the Eclipse application uses Temurin 17.0.9

• Run
• Run configurations...
• Choose our Eclipse Application
• Java Runtime Environment
• Runtime JRE: select Temurin 17.0.9
• Apply

8. Start the Eclipse application
   -> Application with sample content

I can also provide the workspace via a GitHub repo, but it is really not more than the wizard for new RCP Applications created.

Expected Results

The Eclipse Application should show the same content as with Temurin 17.0.9.

Actual Results

The Eclipse Application showed an empty screen with Temurin 17.0.10.

What Java Version are you using?

openjdk version "17.0.10" 2024-01-16 OpenJDK Runtime Environment Temurin-17.0.10+7 (build 17.0.10+7) OpenJDK 64-Bit Server VM Temurin-17.0.10+7 (build 17.0.10+7, mixed mode)

What is your operating system and platform?

OS: MacOS Sonoma 14.3
Platform: MacBook Pro M2, 2023

How did you install Java?

Homebrew

Did it work before?

Yes it worked with Temurin 17.0.9.
I made an update via Homebrew.

Java itself seems to work with Temurin 17.0.10 only the Eclipse RCP application has problem or maybe it has something to do with SWT?

Did you test with other Java versions?

openjdk version "17.0.9" 2023-10-17
OpenJDK Runtime Environment Temurin-17.0.9+9 (build 17.0.9+9)
OpenJDK 64-Bit Server VM Temurin-17.0.9+9 (build 17.0.9+9, mixed mode)

Relevant log output

No response

[karianna]

@ivy-lli - This might be a Eclipse RCP bug (they call out to SWT/native code). Have you reported this to them? Are there any other messages in the Eclipse IDE log files?

[ivy-lli]

Yes of course that is possible too. I thought as this appears when I change the temurin version it is more likely a bug here, but I'm not sure.
Sadly I didn't see any errors in the system output or a log file.
Should I open an issue on the eclipse swt platform too?

[karianna]

Yes of course that is possible too. I thought as this appears when I change the temurin version it is more likely a bug here, but I'm not sure. Sadly I didn't see any errors in the system output or a log file. Should I open an issue on the eclipse swt platform too?

Yes please and they'll come back to us if it's a Temurin crasher.

[Phillipus]

I am getting the exact same problem.

Also with Temurin 21.0.2+13 (but OK with 21.0.1+12).

eclipse-platform/eclipse.platform.swt#1012

Simple steps to reproduce (on macOS Sonoma):

1. Install Temurin JDK 17.0.10+7 or 21.0.2+13
2. Install vanilla Eclipse SDK for macOS here
3. Add Temurin JDK to Eclipse from Eclipse's Settings - Java -> Installed JREs - Add
4. Create a new Debug Launch Configuration of product org.eclipse.sdk and Runtime JRE of the Temurin JDK
5. Launch child Eclipse from this configuration

[Phillipus]

@ivy-lli - This might be a Eclipse RCP bug (they call out to SWT/native code). Have you reported this to them? Are there any other messages in the Eclipse IDE log files?

This is only happening since Temurin 17.0.10+7 and 21.0.2+13. Previous versions are OK. Has there been a change in these versions that might have triggered this problem?

[Phillipus]

I think the difference is that the java binary in latest Temurin is built using macOS SDK 14, previous versions were built using SDK 11 (vtool -show bin/java will show this).

[karianna]

Could well be that its expecting a new API path/call? I'm not familair with Mac OS X changes in this space. https://bugs.openjdk.org/issues/?jql=text%20~%20macos14%20ORDER%20BY%20updated%20DESC might also be worth scanning (recent issues against macosx14)

[Phillipus]

This has got nothing to do with the JDK, only that Eclipse SWT is not handling using a later macOS SDK (14) on the java binary. The same is true if Eclipse is launched with its own launcher binary when that is compiled with macOS SDK 14. See my comments here.

[karianna]

@Phillipus Thanks, I'll close this for now.