Skip to content

The splash screen size is updated after a while during startup and displayed incorrectly. #2851

Open
Open
The splash screen size is updated after a while during startup and displayed incorrectly.#2851
Labels
bugSomething isn't working

Description

@MLausberg
MLausberg
opened on Aug 4, 2026

Steps to reproduce

From a fresh installation and clean workspace:

Adapt the *.ini file used to start the eclipse based application and add
-Dswt.autoScale.updateOnRuntime=false
-Dswt.autoScale=125

At the begining the splash screen is shown correctly, but after some seconds and shortly before the application is shown, the splash screenis redrawn and out of scope.

First

Image

after a while

Image

Splash Screen related

From Product Definition file

   <splash
      location="<obfuscated>" />
Image

Tested under this environment:

Windows 11

Java Version

  • IMPLEMENTOR="Eclipse Adoptium"
  • IMPLEMENTOR_VERSION="Temurin-25.0.1+8"
  • JAVA_RUNTIME_VERSION="25.0.1+8-LTS"
  • JAVA_VERSION="25.0.1"
  • JAVA_VERSION_DATE="2025-10-21"

Eclipse-RCP Back-End (2025-12)

  • org.eclipse.equinox.simpleconfigurator.configUrl=file:org.eclipse.equinox.simpleconfigurator/bundles.info
  • osgi.bundles=reference:file:org.eclipse.equinox.simpleconfigurator_1.5.700.v20251111-1031.jar@1:start
  • osgi.bundles.defaultStartLevel=4
  • osgi.framework=file:plugins/org.eclipse.osgi_3.24.0.v20251126-0427.jar
  • osgi.framework.extensions=reference:file:org.eclipse.osgi.compatibility.state_1.3.0.v20251022-1724.jar
  • osgi.splashPath=platform:/base/plugins/obfuscated

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.

Activity

  1. MLausberg
    added
    bugSomething isn't working
    on Aug 4, 2026

  2. vogella commented on Aug 4, 2026

    @vogella
    vogella
    on Aug 4, 2026
    Contributor

    IIRC HDPI handing had a splash screen bug, try with 2026-06 should be fixed in latest release. Open if you still see it with latest release.

  3. vogella
    closed this as completedon Aug 4, 2026

  4. MLausberg commented on Aug 4, 2026

    @MLausberg
    MLausberg
    on Aug 4, 2026
    Author

    I am sorry, but the same problem exists within 2026-06

    -startup
plugins/org.eclipse.equinox.launcher_1.7.100.v20251111-0406.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.3.0.v20260203-2149
    • org.eclipse.equinox.simpleconfigurator.configUrl=file:org.eclipse.equinox.simpleconfigurator/bundles.info
    • osgi.bundles=reference:file:org.eclipse.equinox.simpleconfigurator_1.5.700.v20251111-1031.jar@1:start
    • osgi.bundles.defaultStartLevel=4
    • osgi.framework=file:plugins/org.eclipse.osgi_3.24.200.v20260515-1403.jar
    • osgi.framework.extensions=reference:file:org.eclipse.osgi.compatibility.state_1.3.0.v20251022-1724.jar

  5. MLausberg commented on Aug 4, 2026

    @MLausberg
    MLausberg
    on Aug 4, 2026
    Author

    I can not re-open this Bug

    Image

  6. HeikoKlare commented on Aug 4, 2026

    @HeikoKlare
    HeikoKlare
    on Aug 4, 2026
    Contributor

    Have you properly considered the information given in the news entries on this topic?

    In particular, are you running the process with the correct/expected DPI awareness?

  7. vogella
    reopened this on Aug 4, 2026

  8. MLausberg commented on Aug 5, 2026

    @MLausberg
    MLausberg
    on Aug 5, 2026
    Author

    Have you properly considered the information given in the news entries on this topic?

    In particular, are you running the process with the correct/expected DPI awareness?

    The parameters I used were specified above.

    • -Dswt.autoScale.updateOnRuntime=false
    • -Dswt.autoScale=125

    As a user, I would expect the splash screen to either be initially too large and not fully visible, or to be displayed correctly from the beginning.

    However, the fact that the splash screen changes its layout during the startup procedure is unexpected and difficult for the user to configure via parameters.

    From your point of view, is there a combination of parameters that corrects the initially described behavior?

  9. HeikoKlare commented on Aug 5, 2026

    @HeikoKlare
    HeikoKlare
    on Aug 5, 2026
    Contributor

    It's not necessarily only about parameters passed via ini, but about the DPI awareness that your process is running. I do not know how you may have configured your product's executable regarding DPI awareness, but with Equinox default settings it is supposed to just work.

    I have just tested with the parameters you have posted used in a current I-Build, and the splash screen works expected (rendered at 125% and preserves its size), so I cannot reproduce the issue you report.
    I am not sure if you have fully moved to a 2026-06 release or just exchanged the Equinox launcher for testing. The latter will not work, because the Equinox launcher behavior and the Eclipse workbench behavior are tighly coupled with respect to the splash, as the splash handle is passed between them and their implementations thus need to align. So you would have to update the workbench to the 2026-06 state as well.

  10. MLausberg commented on Aug 5, 2026

    @MLausberg
    MLausberg
    on Aug 5, 2026
    Author

    I started debugging the Startup process and the Splash-screen size changes after line
    "Workbench.lambda$3(Display, WorkbenchAdvisor, int[]) line: 665"

    if (createSplash) {                                                     
	AUTOSCALE_ADAPTATION.runWithInitialAutoScaleValue(splashCreation);  
}

    Before that line the SplashScreen is
    Image

    after that line is executed the image changes to
    Image

    The Code i am testing and looking at is from 2026-06

    • org.eclipse.ui.workbench_3.139.0.v20260601-0955.jar

    Is the behaviour related to missing/incosistent properties in simpleconfigurator *.xmi file or is this a Bug in the adaption logic?

  11. HeikoKlare commented on Aug 5, 2026

    @HeikoKlare
    HeikoKlare
    on Aug 5, 2026
    Contributor

    As said, for me there is no bug at all. I have downloaded one of the latest Eclipse packages: https://www.eclipse.org/downloads/packages/
    Then I have added to the ini file:

    -Dswt.autoScale.updateOnRuntime=false
-Dswt.autoScale=125

    And everything works as expected.

    Since you seem to be referring to a runtime product started from an IDE, please be aware that no Equinox/application executable with proper DPI awareness is involved here, but the DPI awareness from your JVM process is used. Since all current JVMs default to "PerMonitorV2" (which is inconsistent with the Equinox executable behavior for swt.autoScale.updateOnRuntime set to false), you can experience changing splash screen sizes due to non-fitting DPI awareness of the process and for what Eclipse uses later on. But that is also explained in the already linked news: https://eclipse.dev/eclipse/markdown/?f=news/4.39/platform_isv.md#monitor-specific-scaling-by-default-windows

    If you really want to have a splash screen behavior in your runtime application that conforms to the behavior you will see when using the final Equinox executable, you need to adapt your JVM's manifest to use "System" DPI awareness. But you should be aware that this discrepancy of DPI awareness modes has always existed for the last 10 years and the behavior became even more consistent (except for the splash screen size alignment in very specific configurations like yours) with the latest releases. The behavior of a runtime Eclipse instance and one started via Equinox executable was completely different in terms of DPI awareness / UI scaling until 2-3 releases ago.

    You may also think about replacing a fixed auto-scale zoom with monitor-specific scaling in general, as that fixed-zoom auto-scaling mode is very badly tested and supported in general.

  12. jhgarrison commented on Oct 21, 2026

    @jhgarrison
    jhgarrison
    on Oct 21, 2026

    This has been a problem for at least a year (well, at least since I started using the 125% scaling parameter... age gets us all in the end). Even specifying the High-DPI compatibility option does not fix the issue. On initial launch the splash screen displays correctly; here's what I see after the "select workspace" dialog:

    Image

    In eclipse.ini I have:

    -Dswt.autoScale=125
-Dswt.autoScale.updateOnRuntime=false

    and for High-DPI compatibility settings:

    Image

  13. HeikoKlare commented on Oct 21, 2026

    @HeikoKlare
    HeikoKlare
    on Oct 21, 2026
    Contributor

    Can you explain what you would like to achieve with those settings? Setting a fixed zoom with -Dswt.autoScale is badly supported already. Combining it with custom HiDPI settings for the executable will probably make the behavior even more flaky.

    In case you want to just increase the size of all application to, e.g., 125%, you should consider simply running the Eclipse IDE with default settings. It will use the monitor-specific scaling feature that automatically scales the IDE according to your monitor zoom (125%).
    If you really want to use the -Dswt.autoScale=125 setting, you should at least restore default HiDPI settings for the executable.

  14. jhgarrison commented on Oct 21, 2026

    @jhgarrison
    jhgarrison
    on Oct 21, 2026

    No, I want Eclipse to be 125% upscaled without affecting other apps. Eclipse's default scaling is much too small on my 2560x1440 monitor. This problem seems to affect only Eclipse, other apps are handling the HiDPI display just fine with the global scaling (in Windows) set to 100% so I don't need or want the entire display upscaled, only Eclipse.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions