VS.NET 2003 consume 150MB of physical memory !!!!HELP!!
Ms.net
SLE
> Please, what to do???
>
You could develop smaller applications?
Maybe even write your code with notepad and compile your project using
vbc.exe from the command prompt?
;-))
--
SLE
Herfried K. Wagner
"Ms.net" <ReplyT...@IhateSpam.fuck> schrieb:
> Please, what to do???
What's the problem?
VS .NET is a really big application.
Regards,
Herfried K. Wagner
--
MVP · VB Classic, VB .NET
http://www.mvps.org/dotnet
Nak
Nick.
"Ms.net" <ReplyT...@IhateSpam.fuck> wrote in message
news:uTRSAbo...@tk2msftngp13.phx.gbl...
> Please, what to do???
>
>
Tim Stephenson
"Nak" <a...@a.com> wrote in message
news:eALgt3oV...@TK2MSFTNGP10.phx.gbl...
Ms.net
> Close it, then it wont consume anything.
>
> Nick.
You are really funny :-)
Ms.net
> Buy more memory?
hihihihi;
you r really funny
Iena
"Ms.net" <ReplyT...@IhateSpam.fuck> ha scritto nel messaggio
news:uTRSAbo...@tk2msftngp13.phx.gbl...
> Please, what to do???
>
>
I don'T know why, my VS.NET 2003 consume aboute 60 MByte of memory.... Boh
Fredrik Melin
Thomas Tomicek [MVP]
the debugger.
As a result, any dll loade can never be removed. Every time you start
"debug" and it recompiles, new dll's are loaded -(
--
Regards
Thomas Tomiczek
THONA Software & Consulting Ltd.
(Microsoft MVP C#/.NET)
"Fredrik Melin" <m...@n.o.spam.dacsa.net> wrote in message
news:%23dyp$4yVDH...@TK2MSFTNGP09.phx.gbl...
Fredrik Melin
close it, open it again and so on, if the form has many items on it, it goes
many kb each time.
- Fredrik
"Thomas Tomicek [MVP]" <t.tom...@thona-consulting.com> wrote in message
news:%23cDavZz...@TK2MSFTNGP09.phx.gbl...
Carlos J. Quintero
Is Microsoft aware of this problem?
Carlos Quintero
"Fredrik Melin" <m...@n.o.spam.dacsa.net> escribió en el mensaje
news:eDEVsB4V...@TK2MSFTNGP09.phx.gbl...
Thomas Tomicek [MVP]
leak.
The issue is they only have one appdomain, so they can never unload the
classes. Everytime you open the editor again, basically ,another copy goes
into memory.
--
Regards
Thomas Tomiczek
THONA Software & Consulting Ltd.
(Microsoft MVP C#/.NET)
"Carlos J. Quintero" <carlos_j_quintero@_NO_MORE_SPAM_hotmail.com> wrote in
message news:O8qUeFnW...@TK2MSFTNGP12.phx.gbl...
Carlos J. Quintero
I am not sure if they are related, but I was talking about the memory taken
and not released when, for example, you select all the forms and
usercontrols of a large project in the Solution Explorer (not sure if it
happens with code windows) and you right-click the Open context menu. When
you close all windows, the memory is not released. Are AppDomains involved
here? AFAIK, the IDE is not managed, except some portions. And you seem to
talk about debugged code...
The problem is important because any add-in that behind the scenes opens and
close the designers of all forms and usercontrols, causes the same leak...
did MS provide a fix, workaround or similar?
Thanks in advance,
Carlos Quintero
"Thomas Tomicek [MVP]" <t.tom...@thona-consulting.com> escribió en el
mensaje news:%23mslnap...@TK2MSFTNGP12.phx.gbl...
Thomas Tomicek [MVP]
> Hi Thomas,
>
> I am not sure if they are related, but I was talking about the memory
taken
> and not released when, for example, you select all the forms and
> usercontrols of a large project in the Solution Explorer (not sure if it
> happens with code windows) and you right-click the Open context menu. When
> you close all windows, the memory is not released. Are AppDomains involved
> here? AFAIK, the IDE is not managed, except some portions. And you seem to
> talk about debugged code...
"Some Portions" include the complete design environment. Any addin that
opens/closes the designers works in managed code- the designers ARE managed.