Java Fails to run after using this app (with fix)
Opened this issue · 3 comments
So this was a very odd issue where if I use BetterClearTypeTuner and then try to run "any" java app. The java app just gets hung in the background and I have to kill the task. In this case I was using chatty and the OpenJDK 17 runtime (tried 18,19) This eventually led to me just doing a clean install of windows because I could not figure out what I had changed in my system to break java as it had been a few weeks from running BCTT.
Well on the clean install I again ran BetterClearTypeTuner, but this time I was able to pinpoint the moment it stopped working, after following my fresh install of everything. For whatever reason after I use this program it just hangs. To fix this though I made the assumption that BCTT was creating a value in the registry or somewhere that was causing the java virtual machine to hang, so if I ran MSClearType that's in windows hoping it would it fix it, and it did.
I'm not entirely sure what option is creating or triggering the problem, but if running MScleartype fixes it. Then it might be worth looking into if you want something to troubleshoot. If it's a OpenJDK bug then I could look into filing a bug report on that, because I didn't try other branded JVM, but MScleartype is able to undo whatever BCTT is doing to make it works so it feels like its something BCTT is missing something. I know some options/settings have no visible effects; and remember reading your still filling out some values in case a windows update changes something, but perhaps you might pad more values out, unused or not, in case something obscure like java or other legacy program is looking for the entire string of whatever it expected to make it work.
Hope this report is useful for other even if it's not BCTT fault. Just run MSCleartype to see if it fixes anything.
Very strange. I have no idea what this app could be doing wrong. It would require much deeper inspection of the registry changes performed by the official MS cleartype tuner (my own investigations were limited to looking mainly at registry keys that I found in online documentation, stackoverflow, etc).
I don't have any interest in doing that, so I'll just leave this issue open and see if anyone else knows more.
This happens after resetting to default in the program:
Setting the contrast to 1200 fixed it.
Can confirm, same issue here.