PlatformConfiguration blocks splash screen during startup

[ptziegler]

I think this screenshot describes the problem better than words possibly could:

When launching the Eclipse IDE from my workspace, I usually get stuck with the splash screen for up to two minutes. At least when doing a cold start. If I start it again, it "only" takes ~15s for the application to show up.

Almost all of the time is spent on starting the PlatformConfiguration, which in return is held back by I/O access. This might be a similar problem as #1572.

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.

[merks]

FYI, it sounds like this and you might give the workaround there a try:

eclipse-nattable/nattable#170 (comment)

I believe the general problem is computing the wiring takes super long and that depends on the set of bundles that needs to be wired. The wiring is cached and reused. But then again, maybe this is a different problem, though of course the bundles needs to be inspected to determine the OSGi information...

[laeubi]

@ptziegler Yes loading the bundle groups is expensive, so the goal would be to delay the loading of bundle groups to the point where they are actually needed.

The problem here is the "feature dependent actions" one way would be to compute them in the background and when done trigger an update of the actions.

[vogella]

@ptziegler I have seen long hanging startup during JUnit Plug-ins tests. Setting -Dequinox.resolver.revision.batch.size=1 usually solves that, I debugged that ages ago and for certain run configurations the calculation of the resolver was exploding if done in parallel. Maybe this setting will help you too.