Ghidra: Working at 4k resolution isn't possible

[ValonK]

Describe the bug
after loading the binary and maximizing the window, Ghidra (UI) completely shits the bed and it becomes unusable, which sucks.

To Reproduce
Steps to reproduce the behavior:
run in 4k

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
https://imgur.com/a/kNz2QFc
https://imgur.com/a/Tceevpo

Attachments
If applicable, please attach any files that caused problems or log files generated by the software.

Environment (please complete the following information):

• OS: Windows 10 1809 (Build 17763.379)
• Java Version: 11.0.2 1.8.0_171-b11
• Ghidra Version: 9.0.2

Additional context
Add any other context about the problem here.

[arminfelder]

I guess this is related to #1

[williballenthin]

works for me

[ryanmkurtz]

Thanks @williballenthin. What JDK are you using? OpenJDK, Oracle JDK, Amazon JDK?

[williballenthin]

[ryanmkurtz]

Thanks @williballenthin. @ValonK, you could try the Oracle JDK to see if that fixes it for you. Note that it's up to you to ensure that you meet the licensing requirements for use of the JDK...it can vary from vendor to vendor.

[seritools]

Hi, I've encountered the same problem, weirdly with other Java applications as well. Most of the time it seems to be some breakage with java 1.8+ rendering and multimonitor setups.

Examples of other software having the same behavior:
https://github.com/chatty/chatty/issues/27
https://github.com/fesch/Structorizer.Desktop/issues/536
https://github.com/magefree/mage/issues/1514

In Ghidra, the rendering works just fine for me, until I do the very specific thing of hovering over a button, creating a tooltip that crosses the outside of the window frame, like this:

Immediately after any tooltip crosses the window, every repaint garbles the screen.

Searching for a solution after giving up last time I've found that this seems to work for me: https://github.com/fesch/Structorizer.Desktop/issues/536#issuecomment-397363031

I've added the following lines to support\launch.properties:

VMARGS=-Dsun.java2d.noddraw=true
VMARGS=-Dsun.java2d.d3d=false

It seems to run fine now after setting these VM args.

EDIT: This is on Windows 10 Insider Build Fast, with up-to-date Nvidia drivers.

[arminfelder]

I had the same issue with Ubuntu 19.04, setting

VMARGS=-Dsun.java2d.xrender=true

did the trick for me

[ValonK]

@seritools thanks fixes the problem for me

[ryanmkurtz]

is setting nodraw to true necessary if d3d is set to false? The documentation for nodraw seems to indicate it may not be necessary.

[seritools]

Just checked - VMARGS=-Dsun.java2d.d3d=false seems to be enough 👍

[ryanmkurtz]

Thanks...I'm just trying to narrow down what our default settings should be moving forward, and I can't actually test any of this myself.