Browse by Tags

All Tags » Debugging » ASP.NET Tip   (RSS)
ASP.NET and Performance
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 Read More...
Posted 23 June 08 02:29 by Tom | 2 Comments   
Filed under , , , , , , , , ,
ASP.NET Tips: What to gather to troubleshoot
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 Read More...
Posted 21 May 08 11:38 by Tom | 3 Comments   
Filed under , , , , , , , ,
ASP.NET Tips: What to gather to troubleshoot - part 6 - Recycle due to memoryLimit
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.  Read More...
Posted 20 May 08 12:03 by Tom | 4 Comments   
Filed under , , , , , ,
ASP.NET Tips: What to gather to troubleshoot - part 5 - OutOfMemoryException
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 Read More...
Posted 19 May 08 10:49 by Tom | 8 Comments   
Filed under , , , , , ,
ASP.NET Tips: What to gather to troubleshoot - part 3a - Crash revisited
In the previous post around capturing a dump for a crash, we were talking about using DebugDiag .  But what if we can't use this tool.  There are various reasons for this, maybe we don't want to have it installed on the server, or maybe we are Read More...
Posted 15 May 08 11:11 by Tom | 4 Comments   
Filed under , , , ,
ASP.NET Tips: What to gather to troubleshoot - part 4 - Deadlocks
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 Read More...
Posted 14 May 08 11:35 by Tom | 3 Comments   
Filed under , , , , ,
ASP.NET Tips: What to gather to troubleshoot – part 3 – Crash
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 Read More...
Posted 06 May 08 11:39 by Tom | 5 Comments   
Filed under , , , ,
ASP.NET Tips: What to gather to troubleshoot – part 2 – High Memory
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 Read More...
Posted 05 May 08 09:28 by Tom | 4 Comments   
Filed under , , , ,
ASP.NET Tips: What to gather to troubleshoot – part 1 – High CPU or Hang
On machines running IIS5 and IIS5.1, these are the Inetinfo.exe, DLLHost.exe and/or ASPNET_WP.exe processes. On machines running IIS 6 or 7, this is the w3wp.exe process. The following steps will allow us to get log files of the processes hosting the Read More...
Posted 02 May 08 12:13 by Tom | 12 Comments   
Filed under , , , , , , ,
ASP.NET Tips: Printing an IP Address
So while looking through a dump, you will sometimes come across an IP Address.  For example, the System.Net.IPAddress: If you look at this output, you can see that we have the address in the m_Address field, but what is 1895899146?  This is Read More...
Posted 29 April 08 11:36 by Tom | 4 Comments   
Filed under , ,
ASP.NET Tips: Looking at the finalization queue
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 Read More...
Posted 28 April 08 12:12 by Tom | 4 Comments   
Filed under , , , ,
ASP.NET Tips: How to use DebugDiag to track down where a performance problem is coming from
We recently had a case where the customer was having performance problems. They were seeing requests take a few minutes to return and didn’t know what was happening. So they took some dumps while the problem was happening. So we ran this dump through Read More...
Posted 25 April 08 03:54 by Tom | 7 Comments   
Filed under , , , ,
ASP.NET Tips: How to identify a COM call that is blocking GC, causing a memory leak
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, Read More...
Posted 22 April 08 10:42 by Tom | 7 Comments   
Filed under , , , ,
ASP.NET Tips: Debugger command you may not know about – clientconns
Here is yet another command you may not be aware of.  But it can be really helpful when you are troubleshooting many types of issues with IIS/ASP.NET. !clientconns is part of a debugger extension that ships with DebugDiag .  In the directory Read More...
Posted 14 April 08 05:42 by Tom | 2 Comments   
Filed under , , ,
ASP.NET Tips: Debugger command you may not know about - procinfo
Here is another debugger command that you may not know about that is in the sos.dll file included with the debugger package for .NET 1.0 and .NET 1.1. !procinfo will print out the environment variables, CPU times and memory usage statistics.  This Read More...
Posted 12 April 08 08:48 by Tom | 2 Comments   
Filed under , ,
More Posts Next page »

Search

This Blog

All my posts are provided "AS IS" with no warranties, and confer no rights. All the expressions expressed herein are entirely my own and not necessarily those of Microsoft. In addition, thoughts and opinions often change. Because a weblog is intended to provide a semi-permanent point-in-time snapshot, you should not consider out of date posts to reflect current thoughts and opinions.



Your country's flag: IP Address Lookup





See who links to this blog

Add to Technorati Favorites

site statistics

Technology Blogs - BlogCatalog Blog Directory

Technology
Top Blogs

BlogRankers.com

BRDTracker



Syndication

Page view tracker