TheSwamp
Code Red => .NET => Topic started by: Mark on November 16, 2006, 08:57:34 AM
-
poor subject line I know ...
Why is it when any application that uses .Net is displayed ( as opposed to minimized ) on your screen the memory usage for the app goes way up? For instance, Civil3D can eat up 400 MB of memory in a short time of working with it but if you minimize it the usage drops to 6,000 K! The new PowerShell is the same way, it has some nice features but it is a memory hog! That is until you minimize it.
-
That, sir, is a bug. Map's exhibited this behaviour for years.
-
What about when you maximise it again, I have read somewhere about similar things with .net app's that there is some large memory usage on initial start up for setting up the clr and gc and a minimise/maximise cleans it up substantially.
-
No if I maximize them ( or just make them visible ) again and start working the memory jumps back up.
That, sir, is a bug. Map's exhibited this behaviour for years.
I never noticed that in Map before but I do believe ya. :-)
-
In C3D the worst of it seems to be messing with the AECC points ( dynamic blocks ). They are some how creating groups of these dynamic blocks and they ain't workin all that great if you ask me. I'm guessing dynamic blocks are created with .net.