I've been having less problems with VS crashes lately due to the fact that my memory is running out. This is probably mostly related to the fact that I now have 1GB of memory instead of 512MB than to the fact that Resharper is actually using less memory.
Today I've had to restart VS twice already because I was runing out of memory (making the machine quite slow and then come to a grinding halt). The first signs of this are that the error strip stops updating. At times VS has 500+MB memory in use and at least as much in the swapfile. This still happens only on the project with a lot of large files, but the fact that it's been happening for more than 5 months now is startign to piss me off.
To make sure it's resharper related I've done the following:
- Installed a new machine with just XP2 and VS 2003.
Developed (wasn't nice, but it still works ;)
- Installed resharper (much nicer, but results in low
memory every now and then)
- Removed Resharper (memory usage normal again)
- Installed Coderush (VS takes a bit more memory,
no problems though)
- Installed Resharper (low memory now and then starts to
- Installed other addins (low memory now and then starts
to appear again)
Once the feature freeze starts, please, please, please use you new and nice profiler tool and find those leaks, optimize the damn thing and solve this once and for all.
A little tip ;)
Maybe you could go through the DevExpress Coderush newsgroups, they've had similar problems a year back and posted a lot of their findings there. VS and com don't seem to play nice all the time and leave objects in memory when you don't expect them to be.