Note that there are some explanatory texts on larger screens.

plurals
  1. POExtreme Memory Usage When Debugging Console Apps in Visual Studio 2010
    primarykey
    data
    text
    <p>OK folks, this one is driving me nuts. I have classes that were auto generated by connecting to a third party web service which are fairly large (12 thousand lines and 530k). When I instantiate these classes while <em>debugging</em> in a <em>console</em> app, I can watch the devenv.exe process's mem footprint balloon up to 3GB very quickly.</p> <p>If I run the app from a command line, there are no problems; not even a blip in devenv.exe. There are also no issues if I instantiate the classes in a web app whether or not I am in debug mode.</p> <p>Odder still, I have found that, very rarely (twice out of maybe 50 times that I have tested this out today), after reproducing the issue on a console app, the issue will suddenly start happening on any web app in the same solution. This is easily remedied by opening the solution properties and switching the configuration from Debug to Release and then back to Debug (that took a bit of fiddling and dumb luck to discover).</p> <p>Maddeningly, this only seems to happen on <strong>one</strong> machine so I believe the issue to be something environmental either in the OS or VS. I have reset all VS settings back to defaults with no luck.</p> <p>This machine <em>is</em> the only one with VS 2012 installed (thought it has rarely been used and this solution has never been opened with it) so I am now wondering if that could be the culprit somehow.</p> <p>My next step will be to uninstall/re-install VS2012 to see what happens, but I wanted to get this question out there to see if anyone thinks of something simple that I have not thought of.</p> <p>Edit: I am running VS2010 Pro SP1 32bit on Win7 Pro SP1 64 bit.</p>
    singulars
    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.
 

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