System.Text.EncoderExceptionFallback

Today I found the following e-mail in my inbox: Hello According to this article, http://blogs.msdn.com/b/johan/archive/2008/01/31/using-windbg-hunting-exceptions.aspx written by you, you write that there are three “ever-present exceptions”, I can see why they have to be on the heap, but why is 790ff624 3 36 System.Text.DecoderExceptionFallback 790ff5d8 3 36 System.Text.EncoderExceptionFallback Also always there? I always see them…

0

Make sure you have an Internet connection when using signed assemblies

A customer called in the other day and told me that his web application took a long time to start. My initial thought was (off course) that it was a matter of the classic slow-to start web services I’ve written about earlier. (What to do about the slow startup of web services) As I learned…

1

Investigating Locks

Consider the following scenario: You have an ASP.NET application which intermittently responds sluggishly. As the problem occurs memory usage is about average, as is CPU usage, but still certain pages respond slower and slower. The machine acts just as if it is under heavy load, but judging from the CPU it isn’t. In fact CPU…

2

Walkthrough – Troubleshooting a native memory leak

Problem: A customer called in. They had a Web Service running on a single IIS6. Memory usage would slowly increase and not be released. As a workaround they’d currently set the application pool to recycle at 500 MB, causing a few failed requests upon each restart. I thought I’d describe how I went about troubleshooting…

23

Using WinDbg – Hunting Exceptions

Prerequisites This post will require some basic knowledge of windbg and the sos extension. For this I recommend looking at the following posts: Getting started with WinDbg – Part I Getting started with WinDbg – Part II For more information on Exceptions in general and why they should be avoided I’d like to recommend this post:…

9

Using WinDbg – Advanced commands

Did you know you can build your own advanced commands using for each, if, etc? The complete list of control tokens are: .if .else .elseif .foreach .for .while .do .break .continue .catch .leave .printf .block Using these command tokes you can send quite advanced instructions to the debugger that not only will make your job…

11

Getting started with windbg – part II

This is a continuation of my previous post with the imaginative name Getting started with windbg – part I. I’ll be assuming that you’ve read it, so if you haven’t I suggest you check it out first. We’re still working with the same sample dump, so I’ll pretty much pick up right where we left…

12

Getting started with windbg – part I

Okay, I’ve previously written some random posts about how to set up windbg and how to troubleshoot OutOfMemoryExceptions. I thought I’d take a few steps back and review some of the basics in order to help you get started on using this fantastic tool. Basic Configuration Copy sos.dll from the framework directory to the folder…

43

How to install Windbg and get your first memory dump

Install Windbg Windbg is the tool for the ASP.NET support engineer. It is free and it’s available at www.microsoft.com/whdc/devtools/debugging/default.mspx. The learning curve is steep to say the least, but if you’re interested in finding out what is going on behind the scenes in your application, then Windbg is your new best friend. For information on…

17