Phil has the right of it. SetProcessWorkingSetSize(hProcess, (SIZE_T)-1,
(SIZE_T)-1) is a moderately well-known trick for making desktop apps be
better citizens.

--
/George V. Reilly  [EMAIL PROTECTED]
http://www.georgevreilly.com/blog



Wilson, Phil D wrote:
I always thought it was  SetProcessWorkingsetSize (process handle, -1,
-1) ...... Same effect I'm thinking.

Phil Wilson

-----Original Message-----
From: Discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Dean Cleaver
Sent: Tuesday, January 24, 2006 11:40 AM
To: [email protected]
Subject: Re: [ADVANCED-DOTNET] Visual Studio 2005 consumes ALL computer
memory (RAM and virtual)

It's a very old Windows trick. Basically, all it's doing is calling
"EmptyWorkingSet" on minimise - you can call those APIs yourself if you
want to. I do in my projects, especially the ones that work on Terminal
Services.

[DllImport("psapi.dll", SetLastError=true)] private static extern int
EmptyWorkingSet(IntPtr Process);

Dino

-----Original Message-----
From: Discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Georg Jansen
Sent: Wednesday, 25 January 2006 08:35
To: [email protected]
Subject: Re: [ADVANCED-DOTNET] Visual Studio 2005 consumes ALL computer
memory (RAM and virtual)

The same happens with Excel, maybe some new coding standard in
Redmond...?
btw: The wm size is not reduced much.

Regards
Georg
www.l4ndash.com - Log4Net Dashboard


-----Original Message-----
From: Discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Vince P
Sent: 24. januar 2006 20:18
To: [email protected]
Subject: Re: [ADVANCED-DOTNET] Visual Studio 2005 consumes ALL computer
memory (RAM and virtual)

I can't stop minimizing and restoring.  It's crazy.


-----Original Message-----
From: Discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Julia Lerman
Sent: Tuesday, January 24, 2006 1:21 PM
To: [email protected]
Subject: Re: [ADVANCED-DOTNET] Visual Studio 2005 consumes ALL
computer memory (RAM and virtual)

Hey, what an insane but great trick. I was watching my own devenv hang



out at about 279,000 k and it just went down to 27K after minimizing.

I'm still biting my tongue over the "just change everything to C#"
"solution"....

julie lerman

-----Original Message-----
From: Discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Vince P
Sent: Tuesday, January 24, 2006 1:51 PM
To: [email protected]
Subject: Re: [ADVANCED-DOTNET] Visual Studio 2005 consumes ALL
computer memory (RAM and virtual)

That's a good trick.. I just did that and my memory consumption went
from 189MB of RAM to 17MB.



-----Original Message-----
From: Discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Peter
Ritchie
Sent: Tuesday, January 24, 2006 11:56 AM
To: [email protected]
Subject: Re: [ADVANCED-DOTNET] Visual Studio 2005 consumes ALL
computer memory (RAM and virtual)

Try minimizing Visual Studio then restoring to see if the

memory usage

goes now noticably when you find its memory usage to be high.


On Tue, 24 Jan 2006 18:32:46 +0100,

=?ISO-8859-2?Q?Stanislav_Pe=BBko?=

<[EMAIL PROTECTED]> wrote:


Hello all.

I have a quite big probelm with Visual Studio 2005. I

program in Visual

Basic and VS consumes all my memory, both RAM and virtual.

I monitor

devenv.exe process in Task Manager. When I start VS and load

a solution

(it's not so big), it occupies aproximatly 130 MB of RAM and

the same

amount of virtual memory. As I work, both of them goes up.

And I do

just simple things .. say I have 4 tabs with source code

opened and I

edit one of them. Occupied memory raises and very soon (up

to 1 hour)

the devenv.exe process has all RAM memory (I have 512 MB in

system and

the process takes cca 350 MB) and even all virtual memory

(about 1 GB).

I have to turn VS on and off, because otherwise it crashes.

:-( I don't

need to say you that work is very slow and restarting VS

is annoying.

At home I have the same problem with Visual Basic 2005 Express.


Did anybody encounter this problem? Thanks a lot for any response.



Some technical info:

Visual Studio: VS 2005 Professional Edition, Version 8.0.50727.42
Framework: 2.0.50727
Language: Visual Basic

Hardware: AMD Sempron 2800+ (2 GHz), 512 MB RAM



Stano


PS: Well. I know, 512 MB of RAM is not too much fo VS and

very soon I

will get 1 GB, but I don't thing that it will solve my problem.

===================================
This list is hosted by DevelopMentorR  http://www.develop.com

View archives and manage your subscription(s) at

http://discuss.develop.com

===================================
This list is hosted by DevelopMentorR  http://www.develop.com

View archives and manage your subscription(s) at
http://discuss.develop.com

===================================
This list is hosted by DevelopMentorR  http://www.develop.com

View archives and manage your subscription(s) at
http://discuss.develop.com

===================================
This list is hosted by DevelopMentor.  http://www.develop.com

View archives and manage your subscription(s) at
http://discuss.develop.com


===================================
This list is hosted by DevelopMentor.  http://www.develop.com

View archives and manage your subscription(s) at
http://discuss.develop.com

===================================
This list is hosted by DevelopMentor(r)  http://www.develop.com

View archives and manage your subscription(s) at
http://discuss.develop.com

===================================
This list is hosted by DevelopMentor(r)  http://www.develop.com

View archives and manage your subscription(s) at
http://discuss.develop.com

===================================
This list is hosted by DevelopMentor®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com



===================================
This list is hosted by DevelopMentor®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com

Reply via email to