[gui] The GUI page displays ghosting.

[ChanChuRen]

Issue details

When I use jadx-gui-1.5.0-no-jre-win.exe on a 2k resolution screen, I encounter display component ghosting issues. The problem persists even when I switch the screen to 1080p. However, using jadx-1.4.7.zip works fine at 1080p, but ghosting still occurs when switching to 2k resolution. I haven't found similar issues reported. Initially, I thought it was a problem with my running environment, so I switched between several JDK versions, but the issue persisted. I also tried running two other GUI programs written in Java, and they displayed correctly, which makes me very puzzled. I hope to get an answer from you.

Jadx version

1.5.0

Java version

11.0.16

OS

• Windows
• Linux
• macOS

[jpstotz]

Your screenshot looks a bit like the one in issue #1993.

As you have already tried different Java versions (I assume you tested versions like 17 and 21) you could also check if the used Jadx theme has an impact on your problem (e.g. using default).

In 1080p and 2k resolution what Windows scale factor do you use (100/125/150/175%)?

[ChanChuRen]

I found the reason. As you mentioned, it is related to the theme. I don't know why the default theme wasn't being used; instead, it was the FlatLaf Light theme. Based on my tests, this theme consistently triggers the ghosting issue when using the search function. This problem is not related to the JDK version, monitor resolution, or scaling. After switching to the default theme, the issue was immediately resolved. Thank you very much.

[jpstotz]

You can also try the latest unstable build https://nightly.link/skylot/jadx/workflows/build-artifacts/master

It uses a newer version of the FlatLaf theme library.

[ChanChuRen]

Thank you, I will give it a try.

[skylot]

@jpstotz I checked latest unstable build (with JRE 21) and this issue appear on 'default' theme as well as on FlatLaf themes.
Also, I tried JVM flags from #1993 (comment) and it resolves the issue 🎉

"-Dsun.java2d.noddraw=true"
"-Dsun.java2d.d3d=false"
"-Dsun.java2d.ddforcevram=true"
"-Dsun.java2d.ddblit=false"
"-Dswing.useflipBufferStrategy=True" 

I will try to investigate these flags and why they help, but at least for now we have a workaround 🙂