Can you get this?
Here ya go:
hs_err_pid23144.log (568.2 KB)
Looks like this JDK bug:
We can lean on our vendor a little but there's not a ton we can do.
I wouldn't advise this as a long term solution, but you could try swapping the awt.dll from an older runtime folder in the .ignition cache in to overwrite the one in the latest. No idea if that would even do anything.
Pssst! Windows
Run your designer(s) in Linux.
2 Likes
Where you'll get a whole new but different set of issues to deal with 
Unless you're on a low DPI screen and still running Xorg, perhaps.
Why yes. Twin 4K x 32" monitors counts as low DPI, I guess. And Xorg's stability mocks Wayland adopters. (To which I will switch when it is ready.)
(Debian Bookworm w/ KDE desktop now-a-days, FWIW. No snaps.)
I guess low vs high DPI is not really relevant, it's just whatever system-wide scaling or Xft.dpi changes you need to make.
I had a 32" @ 4K screen at one point and pretty sure I had to run it at the equivalent of 125% scaling to seem like everything was the right size for me.
Interesting. I use 100%. I have to wear reading glasses anyways, so I put the extra real estate to good use.
I think 100% was okay but with the font DPI bumped from 96 to 120? It was a while ago that I had that setup.
For a while I started using a single 32" @ 6K monitor, which was great because that's an even 200% scaling, which works pretty well even on Wayland.
Now I'm using 2x 27" @ 4K, which requires 150% scaling, and really falls apart for most Java stuff on Linux. IntelliJ is the only thing that kind of works with fractional scaling.
1 Like