Mark a specific crash cause for dump capture If you would like to capture dumps for all crashes, clear the ' Save dump files for marked crashes only' checkbox. This requires LeanSentry to observe a crash before your can enable dump capture.

Note that by default, LeanSentry will only capture dump files for specific crashes you mark in the next step. You can select whether you'd like to save the dumps locally on the server, or to upload them to LeanSentry so your developers can download them.Ĭlick 'more settings' to view the dump capture settings. Open the Crash diagnostic settings and enable dump capture.

Locate a crash report and download the dump file.Įnable dump capture for Crash diagnostics.

Mark a specific crash cause for dump capture.

Enable dump capture for Crash diagnostics.

To debug production crashes in Visual Studio, follow these steps: Debugging a production crash in Visual Studio This way, the developer can inspect the state of application code in detail to figure out what led to the crash. In that cause, a developer can use the crash dump associated with the LeanSentry Crash diagnostic report to reproduce the moment of the crash directly in Visual Studio. In some cases however, the crash stack trace may not provide enough information to a developer on WHY the crash took place.

The application code causing crash (or system code where the crash took place).

The cause of the crash (stack overflow, unhandled exception, runtime error, etc).

The crash report provides enough information to fix most crashes, by providing: (Alternatively, you can select your website and go to it's ' Crash diagnostics' tab to view all crashes LeanSentry detected for it.) When a crash takes place in an important website, LeanSentry may notify you, directly including the code causing the crash in the email:Ĭlick the link in the notification email to go to the Crash diagnostic report and see what caused the crash:

Fixing a crash using LeanSentry Crash diagnostics Most APM tools do not detect crashes because the APM code inside the worker process terminates during the crash.īecause LeanSentry is external to your application, it can monitor and automatically diagnose production crashes in the IIS worker process (w3wp.exe). Crashes are a severe issue because they cause aborted requests, loss of state, and in some cases application downtime. A crash is an abnormal termination of the IIS worker process (w3wp.exe) due to an unhandled exception, stack overflow, or other critical failure.

Unhandeld exception. save a crash dump