id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
19169	[PATCH] Modify JavaFxWrapper to better report initialization errors	taylor.smock	Don-vip	"#19044 is getting hit more, and it would be nice to be able to detect the error and fall back to some other behavior (as well as getting a better stack trace).

The patch was originally added to #19114 as a possible method to get a better stack trace, and has been modified to also help plugins fall back to something else instead of crashing (by possibly throwing an exception during initialization).

The better stack trace comes from submitting a FutureTask to the JavaFx Platform.runLater and then performing a `get` on the FutureTask. This should not cause a block in the threads, since the class should not be instantiated inside of the JavaFx Platform thread.

In order to avoid having a bug report on specific exceptions (currently only `NoClassDefFoundError`), they are logged but not sent to the main handler.

TBH, I'd prefer to properly fix #19044, but adding `--add-opens=jdk.unsupported.desktop/jdk.swing.interop=ALL_UNNAMED` to the `jnlp` `java-vm-args` didn't help."	enhancement	closed	normal		Plugin javafx		fixed