PCgen, over a range of retained versions back to 6.05.01, and up to the latest overnight 6.07.02 has been working fine... but now I have accepted Microsoft's compulsory push of the "Creator's Update" - a major update of Win10.
Sadly, now all my versions of PCGen crash with the same error at start-up.
15:43:53.715 INFO main Main:145 Starting PCGen v6.05.01
15:43:53.778 INFO main LanguageBundle:131 Initialising language bundle with locale en_GB.
A fatal error has been detected by the Java Runtime Environment:
EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000005e436adf, pid=8720, tid=0x00000000000025fc
JRE version: Java(TM) SE Runtime Environment (8.0_121-b13) (build 1.8.0_121-b13)
Java VM: Java HotSpot(TM) 64-Bit Server VM (25.121-b13 mixed mode windows-amd64 compressed oops)
Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
An error report file with more information is saved as:
If you would like to submit a bug report, please visit:
The crash happened outside the Java Virtual Machine in native code.
See problematic frame for where to report the bug.
Windows 10 64-bit, Intel Core i7-5820K with 32GB ram
Windows 10 Creator's Update
Java 8 Update 121 build 1.8.0_121-b13 (most up to date)
should have used code not quote:
clean uninstall and re-install of Java. Tried both 32-bit and 64-bit java installs.
Attached 2 hs_err_pidxxx.log files, from the 2 variants of Java. Both crashed.
I'm not hugely familiar with Java debugging and Java logs, but a few salient features stand out:
both variants report access violation, indirecting through NULL
in the JavaThread "Swing-Shell" daemon
Java function is Win32ShellFolder2.getDisplayNameOf(JJI)
in code that's been JIT'ed
There's a bunch of ClassNotFoundException, but I'm making a wild guess that this is "normal" and part of the start up with delayed load???
OK - I think I have pinned down the external cause: if config.ini sets "lookAndFeel=System" then it crashes; with the default "lookAndFeel=Nimbus" it runs. Runs, but looks like Java (meh!).
All my saved installations run with (have been running with!) the System look-and-feel, because, well, it's on Windows!
Fails with Look And Feel set to
Personally I think the LaF code causes more problems than it solves though I tend to be unaware of its main users.
Hopefully will continue working on the JavaFX rewrite. If not, I'll see what I can do about debugging this, but its hard given my general lack of experience, and the fact that my windows computer is a VM.