Jun 25, 2008
There are some times that you want to figure out what is taking up your memory. There are a few ways that you can do this and some limitations put on this by .NET and ASP.NET. Memory in a dump file If you are looking at a dump file, the first thing...
1 comments
Filed under: Debugging, ASP.NET, IIS, .NET, High Memory, Windows
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 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 25, 2008
A common problem we see when moving to .NET all revolves around the finalizer. There are a few reasons that this happens: Developers move from C/C++ to C# and are used to created classes with a constructor and destructor. Developers don’t understand...
1 comments
Filed under: Debugging, ASP.NET, IIS, .NET, Microsoft, High Memory
Apr 22, 2008
Problem Description So this is a customer situation we found were the customer was getting an System.OutOfMemoryException. We were able to reproduce this with a console application that just ran: For Iterator = 0 To 99999999999 Regex.IsMatch(CONNECTION_STRING...
1 comments
Filed under: ASP.NET Tip, Debugging, ASP.NET, IIS, High Memory