Things change and as I always say “that’s better than the alternative”. Although I have yet to put my finger on it, the behavior I experience when debugging Core applications is different than those which have come before. If I ever do figure out the specifics of those differences, I will write them down and […]
Read More →Search Results for: sos.dll
What do C# values look like in WinDbg
One of the important areas you need to master when analyzing memory dumps is to recognize patterns that are normal and not normal. You can only come to those conclusions after looking at many, many, many, many memory dumps and either remembering or taking notes on how a process looks when all is ok, so […]
Read More →Dumping modules from a memory dump for decompilation, decompile
One of my favorite WinDbg commands is the psscor4 SaveAllModules (sam). I used to just bang that one out and use JustDecompile to look at the code to find out what was going on, like why the process was hanging or consuming more memory than expected. At the moment psscor4 does not support the most […]
Read More →Must use, must know WinDbg commands, my most used
I like to write stuff. As I personally use it for reference, instead of keeping it to myself, I often post it onto my blog here. Here is my list of most used WinDbg commands and what information I get for them. I was a big fan of PSSCOR, but since MEX is now a […]
Read More →Troubleshooting a hung or long running WebJob
If you can reproduce the slow running WebJob behavior you have hosted with your Azure App Service Web App, Mobile App or API App then you can find out why using the following article. Additionally, if the WebJob is in a hung state, skip right to the portion where you take the memory dump of […]
Read More →Create a memory dump of your App Service when it consumes too much memory
I have written a number of troubleshooting labs here, one of which is Lab 21: WinDbg – Memory Consumption. In this article I will identify how to capture a memory dump of a process that is consuming too much memory. In this case it is running on an Azure App Service Web App. NOTE: This […]
Read More →Lab 21: Debugging a W3WP process with high memory consumption
Setup: Install Debugging Tools for Windows – for WinDbg Install and configure CSharpGuitarBugs on an IIS server as described in Lab 1 Place PROCDUMP executable on the IIS Server Review memory dump collection process for W2K8 and W2K12 Lab 21.1 Open the main page of the CSharpGuitarBugs website so that a W3WP process is instantiated […]
Read More →Lab 20: Debugging a low CPU hang W3WP process using WinDbg
Setup Install Debugging Tools for Windows – For WinDbg Install and Configure CSharpGuitarBugs on an IIS server as described in Lab 1 Place PROCDUMP executable on the IIS Server Review Memory Dump using PROCDUMP on 2008R2 or 2012R2: Lab Open the CSharpGuitarBugs website Click on the ‘Enter Payment Information’ link and note about how long […]
Read More →Lab 19: Debugging a high CPU hang W3WP process using WinDbg
Setup Install Debugging Tools for Windows – For WinDbg Install and Configure CSharpGuitarBugs on an IIS server as described in Lab 1 Place PROCDUMP executable on the IIS Server Read this HOW TO here. Read about the !runaway command here and copy dbghelp.dll into the c:\temp directory Lab Open Task manager so that the CPU […]
Read More →Lab 7: Integrated versus Classic mode
Prerequisites Read this article about the processModel Read this article about ASP.NET Threads Read this article about Breaking Changes between Classic and Integrated mode See LAB 24: Deploy a Custom Module and Handler, Integrated mode support both Managed and Native Modules, once available Read this article about ASP.NET Page Events Read Contention, poor performance, deadlocks […]
Read More →