Welcome to MSDN Blogs Sign in | Join | Help

Notes from a dark corner

Debugging ASP.NET, the CLR and anything that uses clock cycles.

News

  • These postings are provided as is with no warranties, and confers no rights. Additionally, views expressed herein are my own and not those of my employer, Microsoft.

Browse by Tags

All Tags » Memory   (RSS)
On memory leaks…
If you have a rusty old bucket and it is overflowing because you put too much water in it, then you should certainly think about buying a nice new plastic one at some point. But the new one will still overflow if you put too much water in it. Read More...
Using UMDH to track down native heap memory leaks
No, I'm afraid I haven't taken the time to write about this in detail because Michael Morales has already done a great job of it. Remember though, not all memory leaks are native heap memory leaks. You could also be leaking managed objects (which are Read More...
A long lost friend
I was looking for one of my blog posts the other day that talks about how ASP.NET uses Windows memory. I was hunting and hunting and could not find it anywhere. I finally realised that at some point I had somehow left it in an unpublished state (probably Read More...
New article on debugging .NET memory issues
The latest MSDN Magazine is now published and there is a great article about debugging .NET memory issues: " CLR Inside Out: Investigating Memory Issues ". I've added this to my list of .NET debugging resources which I have now changed from a blog post Read More...
A reading list for debugging, .NET, CLR, WinDBG etc
I'm often asked "Where can I learn more about doing this kind of stuff?", this "stuff" being debugging with WinDBG, understanding how .NET works, looking at dump files and generally figuring out what's gone wrong with .NET applications. I started assembling Read More...
Index of articles on this site
Resources for load testing web applications Resources for debugging .NET with WinDBG etc Read More...
ASP.NET - how it uses Windows memory
Sooner or later you are bound to run into the dreaded OutOfMemoryException and wonder, "why me, why now?". ASP.NET and other web applications are particularly susceptible to high memory consumption because a web application is typically serving 100s or Read More...
Page view tracker