Loading user information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading user information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

Preparing to troubleshoot memory pressure issues: a primer on virtual memory - 10

22 minutes, 18 seconds


Right click “Save as…”

In Part1 of this series, we discussed how most every application issue in production can be listed in one of three buckets: exceptions, non-responsiveness, and performance issues.  This last bucket includes memory pressure issues, which is by far the most common type of .NET application issue I've seen in my time at Microsoft Support.

This episode is the first of three dedicated to troubleshooting memory pressure issues in .NET applications (the kind of troubleshooting Microsoft Support performs in the production environment).  But before we jump straight into the aspects of troubleshooting, it's best to get a good understanding of virtual memory.  Without this background, many of your troubleshooting efforts may lead to dead ends or - even worse - false conclusions.


.NET Debugging for the Production Environment, Part 9

.NET Debugging for the Production Environment, Part 11


Follow the discussion

  • Oops, something didn't work.

    Getting subscription
    Subscribe to this conversation
  • JamesJames

    Excellent foundational expose. Thanks for sharing!

  • RandhirRandhir

    Hey Brad,

    Did you miss posting episode 7, 8, & 9? After 6, the next one shows as 10.


  • Ran@Randhir: Good catch.  Episodes 7-9 have been recorded, but there were issues & need to be re-recorded before I post them.  I should be able to get them published in the next few weeks.

Remove this comment

Remove this thread


Comments closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.