The 21 most popular blog posts


I started this blog 2.5 years ago today, mostly because I felt that the same types of issues came up over and over and over in our support cases. I figured that if I started writing about them, a lot of people would be able to resolve them on their own, or even better avoid them in the first place.

A lot of water passed under the bridge since then, but looking back at some of those earlier posts they are still very applicable today, and they still seem to continue to get a lot of hits.  Here is a list of the 21 most popular ones…

  1. ASP.NET 2.0 Crash case study: Unhandled exceptions
  2. ASP.NET Case Study: Lost session variables and appdomain recycles
  3. ASP.NET Memory: If your application is in production… then why is debug=true
  4. .NET Memory Leak Case Study: The Event Handlers That Made The Memory Baloon
  5. ASP.NET Performance Case Study: Web Service calls taking forever
  6. .NET Memory usage – A restaurant analogy
  7. .NET Garbage Collector PopQuiz – Followup
  8. .Net memory leak: Unblock my finalizer
  9. .NET Hang Debugging Walkthrough
  10. ASP.NET Case Study: Bad perf, high memory usage and high CPU in GC – Death By ViewState
  11. ASP.NET Crash: Bad CacheItemRemovedCallback – Part II
  12. ASP.NET 2.0 – Investigating .NET Exceptions with WinDbg (Compilation and Load Exceptions)
  13. .NET Memory Leak: XmlSerializing your way to a Memory Leak
  14. .NET Garbage Collection PopQuiz
  15. A .NET Crash: How not to write a global exception handler
  16. Things to ignore when debugging an ASP.NET hang
  17. Are you aware that you have thrown over 40,000 exceptions in the last 3 hours?
  18. Short note on some debugging related stuff…
  19. ASP.NET Memory Leak Case Study: Sessions Sessions Sessions…
  20. ASP.NET Case Study: High CPU in GC – Large objects and high allocation rates
  21. A Case of Invalid Viewstate

In 2.5 more years I’ll post the answer to the meaning of life, the universe and everything:)

and…, while I’m on the topic… what would you like to see more of in the future?

Tess

Comments (16)

  1. J.W. says:

    You really had a lot of very impressive posts on topics of debugging. Compared with a lot of books related to debugging, your example-based approach is easier to follow and understand.

    Thanks for all the hard work.

  2. ASP.NET A New Tutorial Series on Master Pages [Via: Scott Mitchell ] Using parent page properties in…

  3. Pedro says:

    Isn’t the answer to the meaning of life, the universe and everything "42"?  I think someone might have beaten you to it  🙂

  4. Tess says:

    exactly:)  21 posts after 2.5 years and 42 posts after 5 years:)

  5. Pedro says:

    Makes sense.  I’ll put that on my calendar right now  🙂

  6. Tim B says:

    I would like to see more tutorials targeted for beginners.  Sort of "introduction to debugging" type posts.

  7. Tess,

    As a part-time programmer, I want to thank you for your continual updates.  They have saved me much time and aggravation.

    Thanks,

    Richard

  8. I’ve just finished writing up an e-mail for some new people in my team about starting Debugging and the

  9. i want to see a post on how debugging can unravel the meaning of life 🙂  

  10. Hello,

    I was looking at you http://blogs.msdn.com/tess/archive/2008/02/27/net-debugging-demos-lab-4-high-cpu-hang-review.aspx article about high cpu and garbage collection.  I was hoping that this was the problem with my application but after analyzing the dump it did not point to gargbage collection.  

    Is there anything else I can look at in the dump to determine why my application has cpu spike every 45 minutes.

    thanks

    brian

  11. When the .NET Framework was first released, many developers believed the introduction of the garbage

  12. When the .NET Framework was first released, many developers believed the introduction of the garbage

  13. When the .NET Framework was first released, many developers believed the introduction of the garbage

  14. Gayatri Pesala says:

    This is a great site for debugging

  15. kiquenet says:

    ***More information***

    asp.net 3.5  vs asp.net 4.0

    My case about ***OutOfMemoryException*** is not memory problem,

    I don't know yet stackoverflow.com/…/outofmemoryexception-using-rdlc-localreport-microsoft-reporting-webforms-in-as

    _Maybe configuration IIS, Pool, web.config issues ?_