EDN Admin
Well-known member
In http://channel9.msdn.com/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01" target="_blank 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, and this is by far the most common type of .NET application issue Ive 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, its 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. <img src="http://m.webtrends.com/dcs1wotjh10000w0irc493s0e_6x1g/njs.gif?dcssip=channel9.msdn.com&dcsuri=http://channel9.msdn.com/Feeds/RSS&WT.dl=0&WT.entryid=Entry:RSSView:b1f5a4b3380b4af9bbc2a0ba0151a71b
View the full article
View the full article