The fix for bug RT-33633 causes a regression of bug RT-15332.

I don't think you can consider catching and logging any exception in a listener notification as good error handling practice. It will cause many real bugs to go totally unnoticed.

In a core architecture like this it is impossible to know the effects of swallowing all exceptions and therefore unecessary to be worrying about notifying the rest of the listeners that are registered. While the FX app thread may not be about to die in these scenarios, as commented in RT-33633, the UncaughtExceptionHandler should still be called since the unexpected exception may render the whole UI corrupt or unstable. The UncaughtExceptionHandler is the only way for an applicaton developer to be notified of unexpected errors so he can notify the user that the application is potentially unstable.