UnobservedTaskException does not catch exceptions from async/await code

[fluentscheduler]

UnobservedTaskException does not catch exceptions from async/await code

[thomaseyde]

After some investigation, I found this event handler to do the trick:

AppDomain.CurrentDomain.UnhandledException

I'm not sure if this handler catches all exceptions, or if we need to use TaskManager.UnobservedTaskException as well.

[tallesl]

When you () => { } the library creates a thread and calls your action on it. If any exception is raised the library is able to catch it and tell you on UnobservedTaskException.

When you async () => { } the library creates a thread that then calls your action which, for being asynchronous, spawns another thread. Since the library don't await your action (it just calls it), the unhandled exception in this second thread crashes the application and you're only able to get a last glance at it on UnhandledException of AppDomain before everything falls down.

Here's a little illustration of what's going on:

static async Task Boom()
{
    throw new Exception("BOOOM!");
}

static void Main(string[] args)
{
    // Bye-bye message
    AppDomain.CurrentDomain.UnhandledException += (sender, e) => Console.WriteLine("Aww, we crashed...");

    Action synchronous = () => Boom().Wait();
    Action asynchronous = async () => await Boom();

    // This one prints "Gotcha!"
    try { synchronous(); }
    catch { Console.WriteLine("Gotcha!"); }

    // This one doesn't print "Gotcha!" and crashes the application
    try { asynchronous(); }
    catch { Console.WriteLine("Gotcha!"); }

    Thread.Sleep(Timeout.Infinite);
}

But don't worry, fixing your example is rather simple:

Schedule(() => {
    var faulty= new FaultyComponent().Run(); // Here the faulty task starts to run on its own thread
    // Do some other stuff
    faulty.Wait(); // Here we join back the faulty task, if any exception were raised you're gonna get it wrapped in an AggregateException
}).ToRunOnceIn(1).Seconds();