Why is it not possible to capture exceptions triggered by async void?

Question

Why is it not possible to capture exceptions triggered by async void?

Asked 7 years, 10 months ago

Viewed 157 times

2

Why it is not possible to capture exceptions triggered by non-recurring asynchronous methods Task?

public async void calcularPrecos()
{
    var tabelaPreco = await getTabelaPreco();
    /* Blá, blá, blá... */
}

public void iniciarCalculos()
{
    try
    {
        calcularPrecos();
        /* Blá, blá, blá... */
    }
    catch (WebException e)
    {
        /* A exceção é disparada mas não é capturada neste ponto. =( */
    }
}

The method getTabelaPreco() requires internet connection, otherwise it triggers an exception of type WebException, but I cannot capture such an exception in try-catch inside iniciarCalculos().

Maybe creating a [mcve] will make it easier to identify the problem.

– Maniero

2016/08/25 at 02:28
Dear @bigown, this is a real example, I thought the consequent lines would not add in solving the problem.

– vinibrsl

2016/08/25 at 02:33
1

If it were real it would give to compile it. I continue with my suggestion to do in the way indicated there. And it is not to put all the code, only the minimum to check the condition of the error, at the moment can not be sure what this code does and why the exception is not captured, it can be up because it was not launched.

– Maniero

2016/08/25 at 02:35
1

Friend, your method iniciarCalculos it is not asynchronous, it will not work right (probably also that this is the problem). Use reserved words async and await in this method just as you did in the calcularPrecos.

– Gabriel Katakura

2016/08/25 at 11:03
Related link https://github.com/dotnet/roslyn/issues/13897

– vinibrsl

2017/07/26 at 20:05

1 answer

Browser other questions tagged c# exception asynchronous task async-await

You are not signed in. Login or sign up in order to post.

by ramaral • **44,197** points · Answer 1 · 2016-08-25T11:05:03+00:00

It is not captured because the method calcularPrecos() returns nothing(void).

For the exception to be propagated it is necessary that it returns Task or Task<T>.

When an exception is launched from an asynchronous task that returns Task or Task <T>, it is captured and placed in the object Task returned.

In the case of methods that return void there is no object Task, therefore, any exceptions launched cannot be captured (except by observing the Appdomain.Unhandledexception Event).

Note that the exception is only released when the task is executed. Try/catch will catch the exception only then.

In his example⁽¹⁾, even if the method calcularPrecos() return a Task, the block try/catch would not capture the exception because, when it occurs, the execution will have already left that block.

So to call the method you have to use await calcularPrecos(); or calcularPrecos().Wait();

See what the documentation says about Async Return Types.

_{⁽¹⁾ See the commenting of Gabriel Katakura.}