-
Bug
-
Resolution: Fixed
-
P4
-
8
-
None
-
Java 1.8.0ea b90
Since bug RT-15332 is fixed I was testing to make sure my application's uncaught exception handler was working properly and I noticed that the only way to have the JavaFX application thread make use of it is to set it specifically using Thread.currentThread().setUncaughtExceptionHandler().
My application already makes use of Thread.setDefaultUncaughtExceptionHandler() to make sure any new threads deal with exceptions in a consistent manner so it would be ideal if the JavaFX thread worked like this as well.
It looks like this happens because JavaFX already sets its own uncaught exception handler which means the thread never delegates handling to its ThreadGroup which would make use of the "default" uncaught exception handler. Plus I believe that the specific JavaFX exception handler is very similar to ThreadGroup's handling when no outside handlers are set...
My application already makes use of Thread.setDefaultUncaughtExceptionHandler() to make sure any new threads deal with exceptions in a consistent manner so it would be ideal if the JavaFX thread worked like this as well.
It looks like this happens because JavaFX already sets its own uncaught exception handler which means the thread never delegates handling to its ThreadGroup which would make use of the "default" uncaught exception handler. Plus I believe that the specific JavaFX exception handler is very similar to ThreadGroup's handling when no outside handlers are set...
- relates to
-
JDK-8095154 javafx.animation.Animation#impl_finished swallows exceptions
- Resolved