I run perfview (default collection only) on a production system where the processor skips up to 100% for a couple of minutes. I get some useful results, but I also get a bunch of BROKEN stacks.
Windows Server 2012 R2 Appliance. The application is exe that starts. The application is compiled in .NET 4.0, but .NET 4.6.1 is running on the server
The perfview assistant says that these BROKEN stacks for my situation have been fixed in Windows 8 (I also assume Windows Server 2012). My dlls are not ngen-ed, but I donβt think it is necessary, as the problem is fixed in Windows 8
Any thoughts?
source share