Note that there are some explanatory texts on larger screens.

plurals
  1. POwindbg cant load sos clr
    primarykey
    data
    text
    <p>I'm not sure that windbg is the right tool, but that's what I'm trying now</p> <p>my asp.net app seems to have a memory leak, it keeps on growing by about 3 MB almost every time a page loads (then it goes back down...)</p> <p>I want to read the entire process memory and see exactly whats being stored that is unnecessary.</p> <p>So I run windbg, attach to the webserver40.exe process</p> <p>then I try</p> <pre><code>.loadby sos clr </code></pre> <p>and I get</p> <p>The call to LoadLibrary(C:\Windows\Microsoft.NET\Framework\v4.0.30319\sos) failed, Win32 error 0n193 "%1 is not a valid Win32 application."</p> <p>Please check your debugger configuration and/or network access.</p> <p>It seems that I have this sos.dll in Framework AND Framework64</p> <p>I tried both using</p> <pre><code>.load C:\Windows\Microsoft.NET\Framework64\v4.0.30319\sos </code></pre> <p>but nothing loads</p> <p>I don't understand why its looking for a vaild 32bit app. im on a 64bit pc with 64bit windows.</p> <p>How can I get this sos thing to load?</p> <p>Also when I start I get this warning</p> <p>WARNING: Process 7240 is not attached as a debuggee The process can be examined but debug events will not be received</p> <p>I also tried <code>loadby sos mscorwks</code> it didn't work, but I understand that was discontinued. I'm in asp.net 4</p> <p>I also read somewhere that the code should be stopped in debug before loading sos, that just hangs VS 2010.</p> <p>Thank you very much.</p> <p>Again, if there's another tool that could better help me, I'm all ears :-)</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload