ASP.NET Tips: What to gather to troubleshoot – part 5 – OutOfMemoryException


So we already talked about what to gather when you are experiencing high memory.  But what if you are actually getting a System.OutOfMemoryException?  Here is how you capture a dump at the time you are running out of memory.

The following steps will configure DebugDiag to automatically capture the memory dump when the System.OutOfMemoryException occurs.

Before the issue occurs

A. Download DebugDiag:
====================

  1. Install the Debug Diagnostic tool
  2. The default installation location for the package is C:\Program Files\DebugDiag. It can be changed.
  3. Make sure any other monitoring and debugging tools are not running.

B. Create a Performance Monitor log:
====================================

  1. Expand Performance Logs and Alerts
  2. Right Click on Counter Logs
  3. Choose New Log Settings...
  4. Enter a descriptive name
  5. Note the log file location for later (or go to the Log Files tab and change the location)
  6. Click the Add button
  7. Click the All Counters and All Instances radio buttons
  8. Select the following from the Performance Object dropdown, being sure to Add each one as you select it:
    • Process
    • Thread
    • Processor
    • Memory
    • .NET CLR Data
    • .NET CLR Exceptions
    • .NET CLR Interop
    • .NET CLR Jit
    • .NET CLR Loading
    • .NET CLR LocksAndThreads
    • .NET CLR Memory
    • .NET CLR Networking
    • .NET CLR Remoting
    • .NET CLR Security
    • ASP.NET
    • ASP.NET Applications
  9. Click Close
  10. Click OK

For the ASP.NET counters, select the version that you are wanting to monitor. Ex. For 1.1 framework, select ASP.NET v1.1.4322 and ASP.NET Applications v1.1.4322.

Note: For more information on Performance monitor, see KB 248345

C. Configure server to capture OutOfMemoryException
===========================================

Add the following registry key. This was added to the .NET Framework so that a breakpoint exception will be thrown when an OutOfMemory condition occurs. This is documented in the following article:

820745 Failfast occurs when you experience an "out of memory" condition

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\
DWord: GCFailFastOnOOM
Value: 2

D. Configure DebugDiag

===================

Configure DebugDiag to capture the memory dump when the BreakPoint Exception is thrown and when the process stops.

  1. Open DebugDiag
  2. On the Rules tab, click Add Rule
  3. Select Crash and click Next
  4. Select All IIS Processes and click Next
  5. Click Advanced Exception Configuration
  6. Click Add Exception
  7. Select Breakpoint Exception, change Action Type to Full UserDump
  8. Click OK
  9. Click Save and Close
  10. Click Advanced Breakpoint Configuration
  11. Click Add Breakpoint
  12. Type KERNEL32!ExitProcess and change Action Type to Full UserDump
  13. Click OK
  14. Click Save and Close
  15. Click Next through the rest of the wizard

Inject LeakTrack.dll to capture native leak information:

  1. Click the Processes tab
  2. Right-click the ASPNET_WP.exe process (or w3wp.exe if running in IIS 6), select Monitor for leaks

After the issue occurs

The memory dump will automatically get captured when the OutOfMemoryException is thrown.

A. Stop the Performance Monitor log

===================================

In Performance Monitor:

  1. Right click on your log that is now listed under Counter Logs
  2. Choose Stop Log

kick it on DotNetKicks.com

Comments (8)
  1. You’ve been kicked (a good thing) – Trackback from DotNetKicks.com

  2. gOODiDEA says:

    DebugASP.NETTips:Whattogathertotroubleshoot-part5-OutOfMemoryException.NETWhyuseth…

  3. gOODiDEA.NET says:

    Debug ASP.NET Tips: What to gather to troubleshoot – part 5 – OutOfMemoryException .NET Why use the Entity

  4. So now that I am done with all the individual posts, I thought I would wrap them all together. 

  5. There are situations when we want to look closely at a process that is running in production environment

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

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

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

Comments are closed.

Skip to main content