# Unplugging kills my designer **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [May 19, 2025, 4:47pm UTC](https://forum.inductiveautomation.com/t/unplugging-kills-my-designer/106421 "2025-05-19T16:47:29Z")\ **Posts on this page:** 9\ **Page:** 2
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [May 21, 2025, 4:56pm UTC](https://forum.inductiveautomation.com/t/unplugging-kills-my-designer/106421/21 "2025-05-21T16:56:50Z")
> [@Benjamin\_Furlani](#): > > `C:\Users\BenFurlani\hs_err_pid23144.log` Can you get this? ---
**Author:** ![Benjamin\_Furlani](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/benjamin_furlani/32/66084_2.png) [@Benjamin\_Furlani](https://forum.inductiveautomation.com/u/Benjamin_Furlani)\ **Post date:** [May 21, 2025, 5:00pm UTC](https://forum.inductiveautomation.com/t/unplugging-kills-my-designer/106421/22 "2025-05-21T17:00:04Z")
Here ya go: [hs\_err\_pid23144.log](https://forum.inductiveautomation.com/uploads/short-url/916oDqI2amnBsi0RDfiRrTJ9aHC.log) (568.2 KB) ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [May 21, 2025, 5:10pm UTC](https://forum.inductiveautomation.com/t/unplugging-kills-my-designer/106421/23 "2025-05-21T17:10:52Z")
Looks like this JDK bug: > **[Loading...](https://bugs.openjdk.org/browse/JDK-8341382)** 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. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [May 21, 2025, 5:24pm UTC](https://forum.inductiveautomation.com/t/unplugging-kills-my-designer/106421/24 "2025-05-21T17:24:41Z")
_Pssst!_ **Windows** Run your designer(s) in Linux. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [May 21, 2025, 5:25pm UTC](https://forum.inductiveautomation.com/t/unplugging-kills-my-designer/106421/25 "2025-05-21T17:25:36Z")
> [@pturmel](#): > > Run your designer(s) in Linux. 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. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [May 21, 2025, 5:28pm UTC](https://forum.inductiveautomation.com/t/unplugging-kills-my-designer/106421/26 "2025-05-21T17:28:00Z")
> [@Kevin.Herron](#): > > 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.) ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [May 21, 2025, 5:30pm UTC](https://forum.inductiveautomation.com/t/unplugging-kills-my-designer/106421/27 "2025-05-21T17:30:35Z")
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. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [May 21, 2025, 5:32pm UTC](https://forum.inductiveautomation.com/t/unplugging-kills-my-designer/106421/28 "2025-05-21T17:32:26Z")
Interesting. I use 100%. I have to wear reading glasses anyways, so I put the extra real estate to good use. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [May 21, 2025, 5:35pm UTC](https://forum.inductiveautomation.com/t/unplugging-kills-my-designer/106421/29 "2025-05-21T17:35:07Z")
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. [Previous page](https://forum.inductiveautomation.com/t/unplugging-kills-my-designer/106421.md?page=1)