Skip to content

Line numbers in editors do not scroll properly on displays with different scaling settings #3039

@lmcbrien-ncs

Description

@lmcbrien-ncs

After updating to Eclipse 2025-06, the line number bar in editors no longer updates properly on my secondary monitor, which has a different scaling setting from my primary monitor.

Screen.Recording.2025-06-12.at.16.24.38.mov

Bug is observed on a Macbook Pro M3 with a retina display (which requires 2x pixel scaling to be usable) and a 2560x1440 monitor running at native resolution. I don't have another system to hand to test with.

I see in the 2025-06 release notes that there is a new Windows-only feature for monitor-specific UI scaling. I have confirmed that the new setting is not visible in Preferences -> General -> Appearance on my Mac OS system.

Steps to reproduce

From a fresh installation and clean workspace:

  • Initial display configuration: primary monitor with 2x display scaling enabled, secondary monitor at native resolution.
  • Open Eclipse.
  • Open or create a text file (e.g. a Java class) that is long enough to require scrolling.
  • Move the Eclipse window to the secondary monitor.
  • Scroll up and down. The main editor pane works normally but the left bar with line numbers, breakpoints, etc is frozen.
  • Move the Eclipse window to the primary monitor.
  • Scroll up and down. Normal behaviour is observed.
  • Change the primary monitor settings to native resolution.
  • Move the window between displays and try scrolling. Normal behaviour is observed.
  • Re-enable display scaling on the primary monitor.
  • Buggy behaviour returns.

Tested under this environment:

  • OS & version:
    • Mac OS Sequoia 15.5 (aarch64)
  • Eclipse IDE/Platform version (as shown in Help > About):
    • First observed after updating to Version: 2025-06 (4.36.0), Build id: 20250605-1316
    • Reproduced on latest integration build Version: 2025-09 (4.37), Build id: I20250611-1800
  • Display:
    • Primary monitor: MacBook M3 Pro (16-inch, Nov 2023) running at default 2x scaling (1728x1117, native resolution 3456x2234)
    • Secondary monitor: Samsung LS27A600NWUXXU running at native resolution (2560x1440)

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingmacOShappens on macOSregression

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions