Errors on restart after update

[jonahgraham]

Let's make sure issue is not already fixed in latest builds first.

• I verified I can reproduce this issue against latest Integration Build of Eclipse SDK

Steps to reproduce

From a fresh installation of eclipse-platform-4.37-linux-gtk-x86_64.tar.gz and clean workspace:

• Add https://download.eclipse.org/eclipse/updates/4.38-I-builds/I20251022-1900/ to available software sites
• Check for updates and complete process
• Restart
• Observe the logged errors and some flashing of the splash screen

I tried

• updating from 4.37 to https://download.eclipse.org/eclipse/updates/4.38-I-builds/I20251021-1800/ and problem does not occur
• problem occurs when updating to latest I-build too.

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.

[jonahgraham]

I have tried looking at the differences between the build inputs but I can't tell what could be a likely change.

eclipse-platform/eclipse.platform.releng.aggregator@I20251021-1800...I20251022-1900

[jonahgraham]

GitHub marked this closed automatically base on a PR being applied in @laeubi fork

Anyway, I would have transferred this to equinox, but that is another org. @laeubi has a fix proposed eclipse-equinox/equinox#1185

[tjwatson]

I'm going to investigate a proper fix. See my comment: eclipse-equinox/equinox#1185 (comment)

[jonahgraham]

I have tried my original bug report, but updating to 2025-12 RC1 and I don't see the problem as badly as before. Java is still being restarted, but I don't see the errors.

Is Java expected to restart multiple times as part of a restart? If so, then this issue is probably complete (although I have never noticed this happen before)

For example, I have this output:

$  ./eclipse/eclipse  -data data -consoleLog
WARNING: Using incubator modules: jdk.incubator.vector
Nov 24, 2025 3:40:53 PM org.apache.aries.spifly.BaseActivator log
INFO: Registered provider org.slf4j.simple.SimpleServiceProvider of service org.slf4j.spi.SLF4JServiceProvider in bundle slf4j.simple
WARNING: Using incubator modules: jdk.incubator.vector
WARNING: Using incubator modules: jdk.incubator.vector
Nov 24, 2025 3:41:41 PM org.apache.aries.spifly.BaseActivator log
INFO: Registered provider org.slf4j.simple.SimpleServiceProvider of service org.slf4j.spi.SLF4JServiceProvider in bundle slf4j.simple

When I watch with a process manager I can see that there are three Java processes:

Original process output:

WARNING: Using incubator modules: jdk.incubator.vector
Nov 24, 2025 3:40:53 PM org.apache.aries.spifly.BaseActivator log
INFO: Registered provider org.slf4j.simple.SimpleServiceProvider of service org.slf4j.spi.SLF4JServiceProvider in bundle slf4j.simple

At this point I say restart after upgrade, and I get the second process output:

WARNING: Using incubator modules: jdk.incubator.vector

And then Eclipse automatically starts again with this output:

WARNING: Using incubator modules: jdk.incubator.vector
Nov 24, 2025 3:41:41 PM org.apache.aries.spifly.BaseActivator log
INFO: Registered provider org.slf4j.simple.SimpleServiceProvider of service org.slf4j.spi.SLF4JServiceProvider in bundle slf4j.simple