Browse by Tags - ASP.NET Debugging - Site Home - MSDN Blogs

ASP.NET Debugging

Debugging from an ASP.NET and Azure Engineer. Posts are from customer issues and things I feel may be useful.

Browse by Tags

Tagged Content List
  • Blog Post: Now Available: Psscor4 – Debugger Extension for .NET 4.0

    I am very happy to announce that Psscor4 is now available for download.  You can download it from: Psscor4 Managed-Code Debugging Extension for WinDbg This should have the same functionality as Psscor2 does but it works against the .NET 4.0 Framework.  Please let me know if you run into any...
  • Blog Post: POP QUIZ: What’s wrong with this code – part 3

    Imagine you are a developer and your boss comes to you complaining that your piece of code has been deemed to be taking up too much memory and causing problems for the application.  You take a look at your code and you see the following, assume that stream is defined above this and is correct: const...
  • Blog Post: High Memory part 6 – Fragmentation revisited

    I have talked about a bunch of commands used to troubleshoot a managed memory problem in the past and given some situations of using them like: High memory, CPU, or other performance problems with .NET High Memory continued - Datatables High Memory part 3 - Native Heap High Memory part 4 - Managed Strings...
  • Blog Post: How do you test the performance of your web site?

    I wanted to get a feel for what tools people are using to test the performance of their website.  My questions are: Do you check page-load times?  Do you dig in to see which files are taking the time How do you track down a page that uses a lot of memory How do you track down a high CPU consuming...
  • Blog Post: ASP.NET Tips: Finding what is taking up memory

    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 you can do is find out how much memory is being...
  • Blog Post: 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 to track down But there are some other things...
  • Blog Post: 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 the type of information you would be sending to Microsoft...
  • Blog Post: 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.  This only applies to the ASPNET_WP...
  • Blog Post: 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 will configure DebugDiag to automatically capture...
  • Blog Post: 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 functioning. On heavily-used sites, a continuous...
  • Blog Post: Understanding when to use a Finalizer in your .NET class

    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 when they need to implement Dispose or Finalize...
  • Blog Post: 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, "/S" ) 'Create a SQLConnection...
  • Blog Post: Chat Question: What extension to use in what situation

    So we have a bunch of debugger extensions that we need to use depending on the situation.  So here are the extensions that can depend on various situations and when to use which.  The first thing to decide is to load the right DLL for the Framework version and Process version: Extension Process...
  • Blog Post: Chat Question: Memory Limits for 32-bit and 64-bit processes

    During our recent blog chat, there were a number of topics that were asked about and I am going to expand on some of them.  The first one is the memory limits for different processes. This really depends on a few different things.  The architecture of the process (32-bit or 64-bit) and also...
  • Blog Post: GDI+ (GdiPlus) and ASP.NET

    So we occasionally see customers that are either using System.Drawing themselves in their ASP.NET application or are using controls (like charting controls) that use it. Under most circumstances, this works just fine.  But there are times where it does not, and this is cautioned to users on the...
  • Blog Post: High Memory part 5 - Fragmentation

    So in our previous High Memory posts, we have talked about situations that are all causes of memory to appear high when looking at the process in Task Manager or Perfmon. But in most situations, you aren't going to be monitoring these tools. So the way you will find out that you are high in memory...
  • Blog Post: High Memory part 4 - Managed Strings

    So the last high memory post, High Memory part 3 , focused on native memory that was the problem, let's get back to our normal, managed world. So other then DataTables which we save in the previous post, High Memory continued , what else could cause us to see a large amount of memory being used by .NET...
  • Blog Post: High Memory part 3 - Native Heap

    So let's continue our digging into Memory problems and how to track down what is happening. So our last post, High Memory continued , went into how to look into the managed heap and if the problem is a System.Data.DataTable, we can look at it and see what the columns are. So what if the memory isn...
  • Blog Post: High Memory continued - Datatables

    So in a previous post, High memory, CPU, or other performance problems with .NET , we began to give some things to look for when dealing with High Memory. So what if debug isn't set and we aren't using debug modules? So the best thing to do first is to try to figure out where all the memory is. For...
  • Blog Post: High memory, CPU, or other performance problems with .NET

    The most common problems we see with ASP.NET (or any .NET application) are high memory and high CPU utilization. The main issue that will cause this is rather simple to fix and rather simple to look for.  Any time there are issues around these things, the very first thing to check is if debug=true...
Page 1 of 1 (20 items)