-
Notifications
You must be signed in to change notification settings - Fork 280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash from SendRequestAsync is unhandled #157
Comments
What version of SDK do you use? Is it server app or desktop/store? |
Not sure on the version. The assembly shows a version of 0.12.0.17386. This is a desktop (C#) app.
From: Sergey Kanzhelev [mailto:notifications@github.com] What version of SDK do you use? Is it server app or desktop/store? — |
@izikl , I believe it was fixed, right? Do you remember exact version? |
Not sure. @RyanSizemore can you upgrade to a stable released SDK? |
@RyanSizemore. Closing the issue, please upgrade at least to the latest stable version. 0.12 is not supported any more. |
@mifurm Application Insights SDK has logic to collect unobserved exceptions. It may indicate a problem with your application. Typically it will happen when Task was started and not awaited for by any code. And this task throws an exception. So there is no code to handle this exception. It may indicate a bigger problem with your code. It's not easy to correlate an unobserver exception with the code that initiated it. Upgrade to 2.4 SDK may help as that version has improved telemetry correlation capabilities. |
Adding server telemetry channel, adaptive sampling and making Active as default configuraiton.
We are seeing a crash in our application with the following stack (we have seen ~3 occurrences of this):
Because the exception occurs in a task and is unhandled, we get a TaskUnobserved exception, resulting in our app crashing. It would seem that some level of try/catch is needed to suppress the exception (probably in the Transmission class), since we have no way to reliably suppress the failure at our app's level.
The text was updated successfully, but these errors were encountered: