![]() ![]() 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |