You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When the code runs to OnUnhandledException in Instrumentation, it not shows the Stats data in the end.
For process exit, it will show the Stats data in the end like:
[info] Stats: Total time: 8810ms | Total time in Callbacks: 68ms [Initialize=3ms, ModuleLoadFinished=28ms/10, CallTargetRequestRejit=4ms/13, CallTargetRewriter=0ms/0....
Expected behavior
Is this expected not showing Stats data when there is unhandled exception?
Screenshots
If applicable, add screenshots to help explain your problem.
Runtime environment (please complete the following information):
I do not understand the problem that you are describing in this issue, other than the output in the application stops when an unhandled exception occurs (which causes the process to terminate). Can you tell us more about the application, the configuration that you are using, etc.? Ideally, please provide a Minimal Reproducible Example of the problem.
ASP.NET Core app does not shutdown the runtime in case of unhandled exception. When you exit the process gracefully shutdown stats are still printed.
Unhandled exception in console app does terminate the program so that .NET native profiler does not execute shutdown. If you want to exit gracefully do use Environment.Exit(1); in AppDomain.CurrentDomain.UnhandledException and shutdown stats are printed.
Bug Report
Symptom
Describe the bug
When the code runs to OnUnhandledException in Instrumentation, it not shows the Stats data in the end.
For process exit, it will show the Stats data in the end like:
[info] Stats: Total time: 8810ms | Total time in Callbacks: 68ms [Initialize=3ms, ModuleLoadFinished=28ms/10, CallTargetRequestRejit=4ms/13, CallTargetRewriter=0ms/0....
Expected behavior
Is this expected not showing Stats data when there is unhandled exception?
Screenshots
If applicable, add screenshots to help explain your problem.
Runtime environment (please complete the following information):
Additional context
Add any other context about the problem here.
Reproduce
Steps to reproduce the behavior:
The text was updated successfully, but these errors were encountered: