xception: Tracking .NET Out-Of-Memory errors

<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener('load', function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <div id="navbar-iframe-container"></div> <script type="text/javascript" src="https://apis.google.com/js/platform.js"></script> <script type="text/javascript"> gapi.load("gapi.iframes:gapi.iframes.style.bubble", function() { if (gapi.iframes && gapi.iframes.getContext) { gapi.iframes.getContext().openChild({ url: 'https://www.blogger.com/navbar/11356004?origin\x3dhttp://openrent.blogspot.com', where: document.getElementById("navbar-iframe-container"), id: "navbar-iframe" }); } }); </script>

Tracking .NET Out-Of-Memory errors

Add the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework

Value name: GCFailFastOnOOM
Value type: REG_DWORD
Value data: 4

The value of "4" writes an event message that includes the size of the allocation that failed and the number of bytes in use. A value of "1" simply logs an event in the Application event log. A value of "2" allows a debugger to be attached.

Use the "4" option to grab a dump, then examine the dump for severe fragmentation of the heap, or an attempt to allocate a huge object.