Still memory usage

Hmmm...

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.

But...

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
appear again)
- Installed other addins (low memory now and then starts
to appear again)

So...

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.

4 comments
Comment actions Permalink

Memory usage optimizations can be expected in about 2 weeks or more (not
earlier). But we will definitely decrease memory use by the release.

Valentin Kipiatkov
Chief Scientist, Vice President of Product Development
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Hmmm...

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.

But...

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
appear again)
- Installed other addins (low memory now and then starts
to appear again)
So...

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.



0
Comment actions Permalink

Caveats: I understand it's a EAP.

I've been running 213 & 214 on a machine with 1GB of memory, in VS.NET 2005.

With ReSharper installed, devenv is runnig somewhere around 400MB, crashes
frequently (6 to 12 times a day), and never shuts down properly.
Without ReSharper, it's running about 120MB, never crashes, and shuts down
properly.

I love ReSharper - it's got great functionality, even with the new
Refactoring VS.NET 2005 offers it adds to my development experience enough
to make it a great product. I'd rather not have to live without it. However,
given the current state of affairs, I can't use it... and I've tried for
weeks.

When is it slated for release?

- Richard


"Valentin Kipiatkov (JetBrains)" <valentin@jetbrains.com> wrote in message
news:3fdb29a69699b8c7b82f7d46f16d@news.intellij.net...

Memory usage optimizations can be expected in about 2 weeks or more (not
earlier). But we will definitely decrease memory use by the release.

>

Valentin Kipiatkov
Chief Scientist, Vice President of Product Development
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>
>> Hmmm...
>>
>> 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.
>>
>> But...
>>
>> 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
>> appear again)
>> - Installed other addins (low memory now and then starts
>> to appear again)
>> So...
>>
>> 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.
>



0
Comment actions Permalink

We are working on it. Memory usage should be reduced in one of the nearest
builds.

Valentin Kipiatkov
Chief Scientist, Vice President of Product Development
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Caveats: I understand it's a EAP.

I've been running 213 & 214 on a machine with 1GB of memory, in VS.NET
2005.

With ReSharper installed, devenv is runnig somewhere around 400MB,
crashes
frequently (6 to 12 times a day), and never shuts down properly.
Without ReSharper, it's running about 120MB, never crashes, and shuts
down
properly.
I love ReSharper - it's got great functionality, even with the new
Refactoring VS.NET 2005 offers it adds to my development experience
enough to make it a great product. I'd rather not have to live without
it. However, given the current state of affairs, I can't use it... and
I've tried for weeks.

When is it slated for release?

- Richard

"Valentin Kipiatkov (JetBrains)" <valentin@jetbrains.com> wrote in
message news:3fdb29a69699b8c7b82f7d46f16d@news.intellij.net...

>> Memory usage optimizations can be expected in about 2 weeks or more
>> (not earlier). But we will definitely decrease memory use by the
>> release.
>>
>> Valentin Kipiatkov
>> Chief Scientist, Vice President of Product Development
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>>> Hmmm...
>>>
>>> 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.
>>>
>>> But...
>>>
>>> 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
>>> appear again)
>>> - Installed other addins (low memory now and then starts
>>> to appear again)
>>> So...
>>> 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.


0

Please sign in to leave a comment.