5

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."

  • IIS 7.5
  • Windows Server 2008 R2 Enterprise

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

Ben Lesh
  • 107,825
  • 47
  • 247
  • 232
  • 1
    Not a real answer hence the comment. I have no experience with CLR profiler but had great results with ants memory profiler http://www.red-gate.com/products/ants_memory_profiler/index.htm (free trial available) – KeesDijk Aug 24 '10 at 14:15
  • Good idea, just tried it, it worked well on my local, unfortunately, it didn't work at all on my production machine, which is what I need. – Ben Lesh Aug 24 '10 at 15:19
  • Hey, any luck yet? I have the same issue with CLR Profiler... – Adi May 10 '11 at 18:01

3 Answers3

7

I've had the same issue. I stoped IIS explicitly myself. Than I was able

Jozef Zelenak
  • 71
  • 1
  • 2
2

Same issue here, the above post helped - I resolved it by running CLRProfiler as 'Administrator'

Caffreys
  • 21
  • 2
2

I've had this problem when using an old, incorrect version of the CLR Profiler (not for use with .NET 4). Make sure you're using the right version of the CLR Profiler for the .net environment you're in:

nairdo
  • 81
  • 6