VS.Net 2003 RAM Usage

  • Thread starter Thread starter Joel
  • Start date Start date
J

Joel

I'm hoping someone can help with an ongoing problem that's been
plaguing me. I'm using VS .NET 2003, coding with Visual C#. I've
found numerous annoying bugs that MS seems to fail to address (hello?
service packs?).

Anyways, what's causing me the most grief is that VS keeps eating more
and more RAM on me, until the system is swapping like mad, and I have
to shut down VS. Once it gets to about 340MB of RAM used, the system
pretty much grinds to a halt. I'm running Windows XP Pro on a P4-2.4
with 512MB RAM. This is the same configuration as the other
developers here, except only one other person is running XP (the
others Windows 2k). I seem to be the only person suffering from this
problem here, and it's driving me nuts. My system is rendered useless
every 30-180 mins.

Any ideas on what I can do to fix this? I've tried running my system
minimally (no extra apps), running in Release mode without the
debugger, installing all updates (including the XP Service Pack 2
SR2), and numerous other things that I've forgotten. I usually have
no more than 2 forms (we're coding with Windows Forms) open at a time,
a few code views, and sometimes a Crystal Report.

Thanks,
Joel
 
What are you using to work out how much RAM it's using?
If your using Task Manager it's wrong, Task Manager reports how much a
program has requested not used.
If thats the case i'd check your system for malware as that's the only
reason my PC ever grinds to a halt.
 
Yeh

I switched to VS2003 because Delphi 8 didn't run anymore on my computer. I
have no difficulties whatsoever. I even find VS the best thing currently
available on the market.

Perhaps you are using third party additions to vs and perhaps these are bad?

kind regards
 
Joel said:
I'm hoping someone can help with an ongoing problem that's been
plaguing me. I'm using VS .NET 2003, coding with Visual C#. I've
found numerous annoying bugs that MS seems to fail to address (hello?
service packs?).

There is a whole portal dedicated at MS to bugs in and around VS.NET:
http://lab.msdn.microsoft.com/productfeedback/

(Funny thing though, I got no worries with VS. I really think it's a great
tool, and I'm using it at least 8h a day, at work and at home.)
Anyways, what's causing me the most grief is that VS keeps eating more
and more RAM on me, until the system is swapping like mad, and I have
to shut down VS. Once it gets to about 340MB of RAM used, the system
pretty much grinds to a halt. I'm running Windows XP Pro on a P4-2.4
with 512MB RAM. This is the same configuration as the other
developers here, except only one other person is running XP (the
others Windows 2k). I seem to be the only person suffering from this
problem here, and it's driving me nuts. My system is rendered useless
every 30-180 mins.

Any ideas on what I can do to fix this? I've tried running my system
minimally (no extra apps), running in Release mode without the
debugger, installing all updates (including the XP Service Pack 2
SR2), and numerous other things that I've forgotten. I usually have
no more than 2 forms (we're coding with Windows Forms) open at a time,
a few code views, and sometimes a Crystal Report.

Maybe you installed something else provoking this behaviour?
I've had a lot of different OS versions and programs on my development
comps, a few with even less memory then 512 megs, and I never had these
problems.
And my config right now is a virtual pc with 400mb ram that I don't even
shutdown anymore, I just save it's state, and it did not eat any memory for
weeks.

But I have not installed SP2 on my working comp's, only on test comps, and I
never use Crystal Reports, so I don't know what these do to your system.

Anyway, in your shoes I would reinstall your whole system. I never bother to
spend days looking for problems in my comps when I can solve it in a few
hours by reinstalling it. Not worth the trouble.

Sam
 
The mere fact that you are the only one suffering
from this problem and others in your group are
okay, is an indication of a malware problem.

Please don't blame MS for this.
 
Back
Top