I am having memory leak issues with my ASP.Net application. I've tried WinDbg, which IMO displays mostly useless information, and I'm currently trying to get the CLR profiler to work.
My problem is everytime I try to "Profile ASP.NET" It just flashes two consoles up so fast I can't read them, then the title bar of the CLR Profiler says "Starting IIS. Error 2 occurred."
Other things to know:
I did try running the CLR Profiler as administrator.
I really need to identify the source of my memory leak, any help would be appreciated.
EDIT:
I've already seen this: http://msdn.microsoft.com/en-us/library/ff650691.aspx
To start debugging, select the profile name in the toolbar, such as <project profile name>, IIS Express, or <IIS profile name> in the toolbar, select Start Debugging from the Debug menu, or press F5. The debugger pauses at the breakpoints. If the debugger can't hit the breakpoints, see Troubleshoot debugging.
I've had the same issue. I stoped IIS explicitly myself. Than I was able
Same issue here, the above post helped - I resolved it by running CLRProfiler as 'Administrator'
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With