Speaking of which...

Sample solutions from Internet development support

Browse by Tags

Tagged Content List
  • Blog Post: 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...
  • Blog Post: Why doesn’t the GC kick in when the worker process is inactive?

    I got the following question in my Getting started with windbg – post and I thought it might be worth posting the replies in a separate article: Hi Johan, about those threads with an ID of XXXX, should they go away after certain amount of idle time like 2 minutes? I am trouble shooting an application...
  • Blog Post: 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...
  • Blog Post: 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...
  • Blog Post: 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...
  • Blog Post: 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 off. More...
  • Blog Post: 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...
  • Blog Post: The standard output buffer-stuffer

    I just closed a case that I thought was a bit interesting. I could skip directly to the old Problem, Resolution format, but I think that most of the time there is a lot to be learned from the troubleshooting process as well, so I'll simply describe the scenario as well as what I did to resolve it. The...
  • Blog Post: I am getting OutOfMemoryExceptions. How can I troubleshoot this?

    Problem: You've written an ASP.NET application that is getting OutOfMemoryExceptions. Cause: Let's find out... Resolution: Use Windbg to take a look at the heap. Is it a leak? Take a look at the memory usage of you application using perfmon. If memory is slowly increasing and never released, then you...
  • Blog Post: 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...
Page 1 of 1 (10 items)