2
Common ASP.NET production
issues and how to troubleshoot
them with WinDbg
Tess Ferrandez - Norlander
Support Escalation Engineer
Microsoft
Session Code: WUX405
9
We will be using
BuggyBits from http://blogs.msdn.com/Tess
Debugging Tools for Windows
SOS.dll
Task Manager
Visual Studio Team System Test
TinyGet
Performance Monitor
Our brains
10
Performance issues
Low CPU => waiting for external resources
and/or locks
High CPU => busy server, infinite loops or high
CPU in GC
15
Crashes and Exceptions
Check out the eventviewer
Disable recycling options
Get memory dump(s)
Look at faulting stacks or logs if neccesary
Use TrackClr.cfg to track exceptions during
testing
16
High memory usage and OOM
Caching and Session State
“Unexpected roots”
Blocked finalizer
DataSet serialization
Large viewstate
Assembly leaks with XmlSerializer
Pinned objects
18
High memory usage and OOM
What are you leaking? (native, .net, assemblies)
Take multiple dumps when memory is raising
and compare
Check the finalizer
Check the Large object heap
Try to group “leaking” objects
Figure out why they are sticking around
(rooted)
19
Remember...
There are tools out there to track down these
types of issues
http://blogs.msdn.com/Tess
Track exceptions during testing with
TrackCLR.cfg
Debugging Tools for Windows