Let's make sure issue is not already fixed in latest builds first.
Steps to reproduce
From a fresh installation of eclipse-platform-4.37-linux-gtk-x86_64.tar.gz and clean workspace:
I tried
I expected: clean startup
But got: many starts of Eclipse/Java (maybe - there are multiple !SESSION entries in the log)
Here is some relevant log output
From the output with -consoleLog I see the following a few times before the platform starts
WARNING: Using incubator modules: jdk.incubator.vector
!SESSION 2025-11-04 14:25:47.732 -----------------------------------------------
eclipse.buildId=4.38.0.I20251024-0020
java.version=21.0.5
java.vendor=Eclipse Adoptium
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86_64 -data data -consoleLog -data file:/tmp/q/data/
!ENTRY org.eclipse.osgi 4 0 2025-11-04 14:25:48.208
!MESSAGE Startup error
!STACK 1
java.lang.NullPointerException: Cannot invoke "org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.removeServiceListener(org.eclipse.osgi.internal.framework.BundleContextImpl, org.osgi.framework.ServiceListener)" because the return value of "org.eclipse.osgi.internal.framework.EquinoxContainer.getServiceRegis
try()" is null
at org.eclipse.osgi.internal.framework.BundleContextImpl.removeServiceListener(BundleContextImpl.java:315)
at org.osgi.util.tracker.ServiceTracker.close(ServiceTracker.java:372)
at org.eclipse.core.runtime.adaptor.EclipseStarter.updateSplash(EclipseStarter.java:1302)
at org.eclipse.core.runtime.adaptor.EclipseStarter.refreshPackages(EclipseStarter.java:763)
at org.eclipse.core.runtime.adaptor.EclipseStarter.loadBasicBundles(EclipseStarter.java:678)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:385)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:294)
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
at java.base/java.lang.reflect.Method.invoke(Method.java:580)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:615)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:563)
at org.eclipse.equinox.launcher.Main.run(Main.java:1415)
at org.eclipse.equinox.launcher.Main.main(Main.java:1387)
Sometimes the Startup error isn't there, but the evidence that there are multiple starts is seeing the following multiple times instead of once:
WARNING: Using incubator modules: jdk.incubator.vector
Tested under this environment:
- OS & version: Ubuntu 25.10
- Eclipse IDE/Platform version (as shown in Help > About): 4.37 -> I20251022-1900
Community
- I understand reporting an issue to this OSS project does not mandate anyone to fix it. Other contributors may consider the issue, or not, at their own convenience. The most efficient way to get it fixed is that I fix it myself and contribute it back as a good quality patch to the project.
Reactions are currently unavailable
Let's make sure issue is not already fixed in latest builds first.
Steps to reproduce
From a fresh installation of eclipse-platform-4.37-linux-gtk-x86_64.tar.gz and clean workspace:
I tried
I expected: clean startup
But got: many starts of Eclipse/Java (maybe - there are multiple !SESSION entries in the log)
Here is some relevant log output
From the output with -consoleLog I see the following a few times before the platform starts
WARNING: Using incubator modules: jdk.incubator.vector !SESSION 2025-11-04 14:25:47.732 ----------------------------------------------- eclipse.buildId=4.38.0.I20251024-0020 java.version=21.0.5 java.vendor=Eclipse Adoptium BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Command-line arguments: -os linux -ws gtk -arch x86_64 -data data -consoleLog -data file:/tmp/q/data/ !ENTRY org.eclipse.osgi 4 0 2025-11-04 14:25:48.208 !MESSAGE Startup error !STACK 1 java.lang.NullPointerException: Cannot invoke "org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.removeServiceListener(org.eclipse.osgi.internal.framework.BundleContextImpl, org.osgi.framework.ServiceListener)" because the return value of "org.eclipse.osgi.internal.framework.EquinoxContainer.getServiceRegis try()" is null at org.eclipse.osgi.internal.framework.BundleContextImpl.removeServiceListener(BundleContextImpl.java:315) at org.osgi.util.tracker.ServiceTracker.close(ServiceTracker.java:372) at org.eclipse.core.runtime.adaptor.EclipseStarter.updateSplash(EclipseStarter.java:1302) at org.eclipse.core.runtime.adaptor.EclipseStarter.refreshPackages(EclipseStarter.java:763) at org.eclipse.core.runtime.adaptor.EclipseStarter.loadBasicBundles(EclipseStarter.java:678) at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:385) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:294) at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103) at java.base/java.lang.reflect.Method.invoke(Method.java:580) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:615) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:563) at org.eclipse.equinox.launcher.Main.run(Main.java:1415) at org.eclipse.equinox.launcher.Main.main(Main.java:1387)Sometimes the Startup error isn't there, but the evidence that there are multiple starts is seeing the following multiple times instead of once:
Tested under this environment:
Community