There have been numerous times where an exception is uncaught and crashes mRemoteNG. While it would be best to have exception handling as close to the throwing code as possible, we need some catch-all exception handling code at the root of the app. It doesn't look good when the app crashes.

Expected Behavior

Uncaught exceptions should trigger a message/dialog that presents the user with what has happened and attempt to ensure that mRemoteNG is still in a usable state. The app should remain running after the exception is shown.

Current Behavior

If an uncaught exception occurs, the app simply crashes.

Context

It is a poor user experience to have an app suddenly crash. In almost all cases we can recover from exceptions with only minor inconvenience.