DebugDiag and MVC4 do not give useful stacktrace

I just experienced a high processor problem on our production server and decided to practice debugging such situations locally in order to be ready for this in the future, but when I try to debug the local MVC4 site, I don’t get the same informative stack trace as the tutorial does .

Question: Does anyone know if it is possible to get a more informative stack trace?

I would expect to see HomeController.Index somewhere, but the only method I see is:

System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion (IntPtr, System.Web.RequestNotificationStatus ByRef)

Local setting

I created a local MVC4 site using .Net 4 running on local IIS 8.0 (NOT iis express) to simulate a server environment. My local machine is running Windows 8 .

Debugging Tool: Debug Diagnostics 1.2

I followed this link: http://www.iis.net/learn/troubleshoot/performance-issues/troubleshooting-high-cpu-in-an-iis-7x-application-pool

In "Figure 6 - DebugDiag Analysis Report". there is a stacktrace screenshot with the top line containing "FastApp._default.Page_Load (System.Object, System.EventArgs).

Screenshot: enter image description here

My screenshot: enter image description here

My code simulating maximum CPU usage:

public class HomeController : Controller { public ActionResult Index(int seconds) { ViewBag.Message = "Modify this template to jump-start your ASP.NET MVC application."; DateTime start = DateTime.Now; while (DateTime.Now.Subtract(start) < TimeSpan.FromSeconds(seconds)) { "".ToString(); } return View(); } } 

Possible duplicate:

DebugDiag does not show .NET stack information in .NET 4

+2
source share
1 answer

Debugging Diag 1.2 may not give you the correct stack traces for .net framework 4.0. This is actually not your correct stack for .net 4.5 at all.

You should use Debug Diag 2.0 to analyze memory dumps oriented to framework 4.0 and higher. You can get the tool from http://www.microsoft.com/en-us/download/details.aspx?id=40336

+1
source

All Articles