Rolls up all the fixes since the last binary release in Jan 2022.
Improved Sandbox for experimenting with code outside the included samples.
Removed some bytecode-driven unit tests that were failing on JDK21 javac output.
These shaded jars include OpenJFX binaries needed for the UI.
Bytecode is Java 8 and runs on JDK8 to JDK23.

To run: java -jar jitwatch-ui-1.4.9-shaded-<OS>-<ARCH>.jar

While testing JITWatch on an Apple M1 CPU (via Scaleway M1 VPS) I found that OpenJFX version 17.0.1 would segfault the VM.

Bumped the version to 17.0.2 which includes a fix for this bug.

Please use the release jitwatch-ui-1.4.7-shaded-mac-m1.jar for an Apple M1 (aarch64) MacOS computer.

• If hsdis is not detected then the JITWatch sandbox will offer to download it from https://chriswhocodes.com/hsdis/
• Fixed broken scripts

This was released earlier as 1.4.5 but had a bug in the filename for the MacOS hsdis plugin. Re-released as 1.4.6

JITWatch now uses my simple, minimal logger com.chrisnewland.freelogj which is a drop-in replacement for SLF4J.

• Shaded jars (for JDK11+) contain only the OpenJFX native binaries for the target platform
• Fixed VM vendor and version display on main UI

A fix rollup build containing:

All the cool i18n contributions
OpenJFX version upgrade to 17.0.0.1
Build fix to add-export to allow JavapTask to be used via reflection again (faster)
All the other fixes since Oct 2020.

This release contains all the fixes since the last release in 2017 plus cleaned up build files and upgrades OpenJFX to 15.0.1 when using JDK11+

Each shaded jar contains all the dependencies including OpenJFX for your operating system so you can now run JITWatch using
java -jar <jarfile>

jitwatch-ui-1.4.0-shaded.jar => Linux
jitwatch-ui-1.4.0-shaded-mac.jar =>Mac
jitwatch-ui-1.4.0-shaded-win.jar => Windows

This release adds 4 new visualisations around the JIT compiler threads and queues.

Explained in this video https://www.youtube.com/watch?v=p0mWUgRcCHQ&feature=youtu.be

When an On-Stack-Replacement (OSR) compilation is selected in the TriView it will now highlight the bytecode and source code of the loop that was compiled.

Use JITWatch in presentations or blogs?
Now you can snapshot the main, TriView, Sandbox, and Compile chain windows.
Saves the time-stamped screenshot to the working directory.