Sign In
If broken it is, fix it you should
Using the powers of the debugger to solve the problems of the world - and a bag of chips by Tess Ferrandez, ASP.NET Escalation Engineer (Microsoft)
Tess Ferrandez
I work as as an Escalation Engineer in the ASP.NET developer support team at Microsoft.
My job is to help developers fix problems (memory leaks, hangs, crashes etc.) in their applications, using troubleshooting tools like debuggers and profilers.
In this blog I share tips and tricks for troubleshooting those issues, along with random tidbits about computing and my life at MS.
If you are new here, start with:
My debugging labs (Buggy Bits)
My Silverlight labs (building a game)
Thanks for visiting my blog
@TessFerrandez
Options
About
Email Blog Author
RSS for posts
Atom
RSS for comments
OK
Search this blog
Advanced search options...
Search In:
Everything
Blogs
Forums
People
Groups
Places
Pages
Date range:
All Time
Last Year
Last 6 Months
Last 3 Months
Last Month
Last Week
Last Two Days
Tags
ASP.NET
Crash scenarios
Debugging
Debugging Labs
General debugging tidbits
Kinect SDK
Memory issues
Pages
Performance issues and hangs
presentation
Silverlight
SOSEX
Archive
Archives
August 2011
(3)
May 2011
(1)
December 2010
(1)
November 2010
(1)
September 2010
(3)
August 2010
(2)
June 2010
(1)
May 2010
(1)
April 2010
(3)
March 2010
(4)
February 2010
(2)
January 2010
(2)
December 2009
(2)
November 2009
(2)
October 2009
(4)
September 2009
(4)
August 2009
(2)
July 2009
(1)
June 2009
(3)
May 2009
(3)
April 2009
(5)
March 2009
(9)
February 2009
(2)
January 2009
(6)
November 2008
(8)
October 2008
(7)
September 2008
(7)
August 2008
(5)
July 2008
(1)
June 2008
(7)
May 2008
(12)
April 2008
(14)
March 2008
(12)
February 2008
(17)
January 2008
(5)
December 2007
(2)
November 2007
(1)
October 2007
(8)
September 2007
(3)
August 2007
(7)
June 2007
(5)
May 2007
(1)
April 2007
(5)
March 2007
(4)
January 2007
(1)
December 2006
(1)
November 2006
(2)
October 2006
(4)
September 2006
(3)
August 2006
(3)
June 2006
(1)
May 2006
(1)
April 2006
(5)
March 2006
(2)
February 2006
(8)
January 2006
(7)
December 2005
(3)
November 2005
(6)
June, 2008
MSDN Blogs
>
If broken it is, fix it you should
>
June, 2008
Posts
Subscribe via RSS
Sort by:
Most Recent
|
Most Views
|
Most Comments
Excerpt View
|
Full Post View
If broken it is, fix it you should
ASP.NET Memory Leak: Byte arrays rooted in System.Security.Policy.Evidence
Posted
over 4 years ago
by
Tess1
6
Comments
Today I got a question from a reader (Chris) about a memory leak they are seeing in their application When we do a '!dumpheap -min 85000 -type Byte[]' we can see 100s of byte array objects using up ~545MB of memory. A majority of the objects are the same size (either 4.5 or 9MB in size). Looking at the memory addresses, they all appear to be different copies of our assemblies. And when we do !GcRoot on those addresses they all either have no results returned, or show a rooted System.Security.Policy...
If broken it is, fix it you should
Bag of Chips: Installing XNA Games on your Zune
Posted
over 4 years ago
by
Tess1
5
Comments
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 about this:) so I'll put this post in the "bag of chips" category... I finally installed the first games on my Zune, and in reality it wasn't even a game, but a clock, a feature that I had really been missing. I am sure that it will get a lot easier as everything goes public but for now, here is what I did to install the games with the...
If broken it is, fix it you should
100% CPU in vbc.exe when compiling large vb.net web applications in Microsoft Visual Studio 2008
Posted
over 4 years ago
by
Tess1
14
Comments
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. Apart from the 100% CPU situation you may also notice symptoms like visual studio taking a very long time to return or error messages like Error 246 Timed out waiting for a program to execute. The command being executed was "C:\Windows\Microsoft.NET\Framework\v3.5\vbc.exe" /noconfig @"C:\TempFiles\MyApp\8ec39ce7\e41b4e32\gpznqwbu.cmdline". or ...
If broken it is, fix it you should
Presenting at TechEd Developers Europe 2008, Barcelona
Posted
over 4 years ago
by
Tess1
0
Comments
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 14th TechEd Developer 2008 is coming to Barcelona, Spain and the session list is already starting to build. This will be my first time at TechEd so I am really excited, especially with it being in Spain (since I'm half Spanish). If you want to check out the sessions that are already posted you can do so here and give feedback...
If broken it is, fix it you should
ASP.NET Case Study: Deadlock waiting in GetToSTA
Posted
over 4 years ago
by
Tess1
8
Comments
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 going on in this case, and as it turned out (this is embarrassing:)) I had already written about the root cause of this issue before ( here ). So what I am learning from this is that perhaps I should at least check my blog before asking questions:) Problem description Intermittently the application will stall, so all requests will hang until...
If broken it is, fix it you should
CLR Inside Out: Large Object Heap Uncovered
Posted
over 4 years ago
by
Tess1
1
Comments
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... ASP.NET Case Study: High CPU in GC - Large objects and high allocation rates ASP.NET Case Study: Bad perf, high memory usage and high CPU in GC - Death By ViewState Maoni just wrote a nice article in MSDN Magazine called CLR Inside Out: Large Object Heap Uncovered , it is definitely worth a read if you are interested in how the GC works and specifically...
If broken it is, fix it you should
Setting .NET breakpoints in Windbg for applications that crash on startup
Posted
over 4 years ago
by
Tess1
4
Comments
I recently received a question from a reader who wanted to know how to set breakpoints in code for applications that crash on startup. The email went like this: I have a .NET app which is crashing upon startup (it even causes DW20.exe to make an appearance). When I open the .NET app in Windbg, I can see exactly what the exception is and where it happens. What I would like to do is put a breakpoint on the method where the exception is being raised so that I can step through it. This is where I'm stuck...
Page 1 of 1 (7 items)