Memory usage
-
I'm in VS2008 and as I debug my project the memory use of devenv keeps increasing until it takes up all of my memory. This never happened in VS2005. Any ideas appreciated.
-
I'm in VS2008 and as I debug my project the memory use of devenv keeps increasing until it takes up all of my memory. This never happened in VS2005. Any ideas appreciated.
-
I'm in VS2008 and as I debug my project the memory use of devenv keeps increasing until it takes up all of my memory. This never happened in VS2005. Any ideas appreciated.
You did buy all the memory, why are you hoping it doesn't get used? Good software takes advantage of available memory, while being willing to give up a lot of it when requested to do so. In that sense VS2008 and Vista are good. They both object to memory holding "nothing". They keep data around like a cache. Experiment: start two instances of Visual Studio and have them both do whatever it was you did with one VS. Each of them will be slightly slower and use less memory than the single one did. Of course, there are also other ways to really waste memory (e.g. memory leaks), where the user is not getting any advantage. Memory wasted like that is unlikely to be recoverable (try minimizing your app and watch what TaskManager says about the working set; mind you, TaskManager is not a very good indicator). :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read code that is properly formatted, adding PRE tags is the easiest way to obtain that.
[The QA section does it automatically now, I hope we soon get it on regular forums as well]
-
You did buy all the memory, why are you hoping it doesn't get used? Good software takes advantage of available memory, while being willing to give up a lot of it when requested to do so. In that sense VS2008 and Vista are good. They both object to memory holding "nothing". They keep data around like a cache. Experiment: start two instances of Visual Studio and have them both do whatever it was you did with one VS. Each of them will be slightly slower and use less memory than the single one did. Of course, there are also other ways to really waste memory (e.g. memory leaks), where the user is not getting any advantage. Memory wasted like that is unlikely to be recoverable (try minimizing your app and watch what TaskManager says about the working set; mind you, TaskManager is not a very good indicator). :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read code that is properly formatted, adding PRE tags is the easiest way to obtain that.
[The QA section does it automatically now, I hope we soon get it on regular forums as well]
OK, but I still don't see why VS2008 should not give memory back. Each time I start the solution more memory is taken by the program. Stopping the program or minimizing it does not give memory back. Eventually Task Manager shows the private working set at almost 2G. Is this really normal behavior? ty
-
OK, but I still don't see why VS2008 should not give memory back. Each time I start the solution more memory is taken by the program. Stopping the program or minimizing it does not give memory back. Eventually Task Manager shows the private working set at almost 2G. Is this really normal behavior? ty
That does not sound all right. It may be a bug in VS. I'm not aware of such bug though. You are aware Visual Studio executes some of your code (such as Form constructors) while you are designing your Forms, so any memory leaks you have in such code would accumulate. Does the memory situation deteriorate when you run your app to completion? or only when it crashes, or you stop the execution prematurely by hitting the "Stop Debugging" menu/icon/key combination? :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read code that is properly formatted, adding PRE tags is the easiest way to obtain that.
[The QA section does it automatically now, I hope we soon get it on regular forums as well]
-
That does not sound all right. It may be a bug in VS. I'm not aware of such bug though. You are aware Visual Studio executes some of your code (such as Form constructors) while you are designing your Forms, so any memory leaks you have in such code would accumulate. Does the memory situation deteriorate when you run your app to completion? or only when it crashes, or you stop the execution prematurely by hitting the "Stop Debugging" menu/icon/key combination? :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read code that is properly formatted, adding PRE tags is the easiest way to obtain that.
[The QA section does it automatically now, I hope we soon get it on regular forums as well]
What's very strange is that the memory use does not increase significantly while I'm running the program but only after I stop it. Within a few seconds after the program stops (no matter whether it breaks or finishes) the memory use goes up substantially.
-
What's very strange is that the memory use does not increase significantly while I'm running the program but only after I stop it. Within a few seconds after the program stops (no matter whether it breaks or finishes) the memory use goes up substantially.
Very strange indeed. Never seen such a phenomenon. :doh:
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read code that is properly formatted, adding PRE tags is the easiest way to obtain that.
[The QA section does it automatically now, I hope we soon get it on regular forums as well]