ASP.NET Memory Leak: Byte arrays rooted in System.Security.Policy.Evidence
Today I got a question from a reader (Chris) about a memory leak they are seeing in their application
Recent Posts
Bag of Chips: Installing XNA Games on your Zune
It is not often that I stray too far from debugging and ASP.NET on my blog, but this time I am going to make an exception because I am just really excited ab...
100% CPU in vbc.exe when compiling large vb.net web applications in Microsoft Visual Studio 2008
We just released a hotfix for an issue where you get 100% CPU in vbc.exe when compiling large applications in Microsoft Visual Studio 2008.
Presenting at TechEd Developers Europe 2008, Barcelona
Save the date! TechEd Developers North America 2008 just finished but there is plenty more to come… I know it’s a bit early still, but November 10th through ...
ASP.NET Case Study: Deadlock waiting in GetToSTA
This is an issue I come across once in a while and since I am not a COM expert by any means I actually had to check in with our COM guys to see what was goin...
CLR Inside Out: Large Object Heap Uncovered
In many of my posts I have discussed performance issues and memory issues caused by excessive use of the Large Object Heap, here are a few examples.
Setting .NET breakpoints in Windbg for applications that crash on startup
I recently received a question from a reader who wanted to know how to set breakpoints in code for applications that crash on startup.
ASP.NET Memory: Thou shalt not store UI objects in cache or session scope
ASP.NET Memory: Thou shalt not store UI objects in cache or session scope Surprisingly the issue I wrote about in the event handlers that made the memory bal...
DebugDiag 1.1 or Windbg, which one should I use? and how do I gather memory dumps
If you have read any of my posts you have probably noticed that I am very partial to windbg and the debugging tools for windows. I often get friendly nudges ...
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 t...