Windbg can not load sos clr

Question

I'm not sure that windbg is the right tool, but what I'm trying to do now

My asp.net application seems to have a memory leak, it continues to grow by about 3 MB almost every time the page loads (then it comes back down ...)

I want to read all the process memory and see what exactly is stored, what is not needed.

So, I run windbg, join the webserver40.exe process

I will try

.loadby sos clr 

and i get

Failed to execute the LoadLibrary call (C: \ Windows \ Microsoft.NET \ Framework \ v4.0.30319 \ sos), Win32 error 0n193 "% 1 is not a valid Win32 application".

Check your debugger configuration and / or network access.

It seems that I have sos.dll in Framework and Framework64

I tried using

 .load C:\Windows\Microsoft.NET\Framework64\v4.0.30319\sos 

but nothing is loading

I do not understand why he is looking for a vaild 32bit application. im on a 64-bit pc with 64-bit windows.

How can I download this sos thing?

Also, when I start, I get this warning

WARNING: The 7240 process is not included as a debug process. You can check the process, but no debug events will be received.

I also tried loadby sos mscorwks , this did not work, but I understand that it was stopped. I'm in asp.net 4

I also read somewhere that the code should be stopped when debugging before loading sos, which just hangs VS 2010.

Thank you very much.

Again, if there is another tool that can help me better, I'm all ears :-)

Answer 1

WebDev.WebServer40.exe is a 32-bit executable file. To debug, you need to use 32-bit WinDbg. Visual Studio, as well as the Callipso server, are still running in 32-bit mode.

On another issue. Yes, WinDbg is a great tool for investigating memory leaks in managed code. This blog will help you get started. However, in your case, I would not be sure that you have a memory leak.

• You say that memory is gradually dropping. This means that this is not a memory leak, because skipped memory is never freed.
• Do not waste your time studying memory problems at Callipso. There are many differences between IIS and Callipso that make your findings inapplicable in a production environment. Even if you find that Callipso is really leaking, it does not mean that IIS will be.