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 19, 2008
So we already talked about what to gather when you are experiencing high memory . But what if you are actually getting a System.OutOfMemoryException? Here is how you capture a dump at the time you are running out of memory. The following steps...
1 comments
Filed under: ASP.NET Tip, Debugging, ASP.NET, IIS, .NET, High Memory, Exceptions
May 14, 2008
There are two ways to gather data in a Deadlock situation. If you are using Windows 2003 or later (IIS 6.0 or later), then follow the steps in the KB 828222 If you are using an older version of IIS, then follow the steps below: Before the issue...
1 comments
Filed under: ASP.NET Tip, Debugging, ASP.NET, IIS, .NET, Hang
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
May 05, 2008
Identifying a Memory leak A Memory Leak in an IIS process (INETINFO.EXE, DLLHOST.EXE, W3WP.EXE) occurs when Memory Usage in Task Manager continues to consume more than 50% of the physical RAM until running out of system memory or until the process stops...
1 comments
Filed under: ASP.NET Tip, Debugging, ASP.NET, IIS, High Memory
Apr 28, 2008
So in a previous post, we talked about Understanding when to use a Finalizer in your .NET class so now lets take a look at what the Finalize queue looks like and how to tell if things are bad. The command we use is !finalizequeue in sos: 0:010> !finalizequeue...
2 comments
Filed under: ASP.NET Tip, Debugging, ASP.NET, IIS, .NET