Sep 25, 2008
There are only a few things that can make a .NET process crash. The most common one is an Unhandled Exception getting raised. Another way that is can happen is by creating a GC Hole. What is a GC Hole So first a little background on what I...
1 comments
Filed under: Debugging, ASP.NET, IIS, .NET, Crash
Jun 23, 2008
I wanted to talk about monitoring performance in ASP.NET for a bit. I have already posted a few postings that talk around this issue, namely: ASP.NET Debugging - High Memory part 5 – Fragmentation ASP.NET Debugging - ASP.NET Tips- How to use DebugDiag...
2 comments
Filed under: ASP.NET Tip, Debugging, ASP.NET, IIS, .NET, Microsoft, High Memory, Hang, High CPU, Crash
May 21, 2008
So now that I am done with all the individual posts, I thought I would wrap them all together. So here are all of the posts that I created on gathering information when you are having a problem. Please keep in mind that these are geared towards...
2 comments
Filed under: ASP.NET Tip, Debugging, ASP.NET, IIS, .NET, High Memory, Hang, High CPU, Crash
May 20, 2008
Here is another situation that you may come across and what to do in order to gather information about it. The following steps will configure DebugDiag to automatically capture a memory dump of the ASPNET_WP.exe process recycling when it exceeds the memoryLimit...
2 comments
Filed under: ASP.NET Tip, Debugging, ASP.NET, IIS, .NET, High Memory, Crash
May 06, 2008
Defining an IIS Crash A Crash in IIS occurs when an IIS process (INETINFO.EXE, DLLHOST.EXE, W3WP.EXE) terminates unexpectedly. A Crash typically happens when there is an Unhandled Exception caused by an Access Violation, Stack Overflow, etc. In these...
1 comments
Filed under: ASP.NET Tip, Debugging, ASP.NET, IIS, Crash