Massive performance problems with 6.1.1!

After working some time with 6.1.1 without problems today i encounter again massive performance problems with the VB editor. I'm working on a refactoring of a large file (around 10.000 lines). I had no problems until i duplicated a method of around 1.000 lines i wanted to refactor. After pasting the code into the editor i changed the method signature. For this reason i got a bunch of errors (> 100). After this VB Editor becomes slower and slower and after some minutes the was an error popup from R# denoting low virtual memory and shortly after that VS crashes with an OutOfMemoryException. This behavior was reproducible each time i restarted VS. I took two performance snapshots with dotTrace which i will upload this evening (can't do this at work). While taking the snapshots VS was very slow but it didn't crashed.

Regards
Klaus


(My configuration is: Visual Studio 2010 SP1 on Windows XP SP3)

7 comments
Comment actions Permalink

Hi Klaus,

Thanks for taking the snapshots!
I can see that the corresponding issue that you've raised has been elevated to show-stopper and is being looked at.

0
Comment actions Permalink

I just had a OutOfMemoryException while editng the same file like yesterday. I've attached a screenshot of the exeption message to the issue i created. Hope this will help you.

Regards
Klaus

0
Comment actions Permalink

Thanks Klaus,

We'll take a look.

0
Comment actions Permalink

This sounds so reminiscent. There is a whole thread running about similar experiences. Resharper Performance

My issues were around Database Projects , and VB Code, but the same experience with C# code as well.

The issue has been around for a while , and is still unresolved.

There was some suspicion from Andre that the File Structure window may have been involved, this feature to me is a Must Have , so cloisng it down negates a lot fo the benefits of the tool.

There is another thread running , asking if we will have to wait and upgrade to V 7 before these issues are fixed in V 6. Maybe you should have look through these too.

Mike

0
Comment actions Permalink

i'm working sometimes with the 7.0er EAP and VS 2011 on the same project i have problems with. The performance is a bit better, but this maybe because my laptop is much more performant than my desktop at work. In my opinion the basic problem is that R# background processing conflicts with VB Editor background processing. The performance snapshots i took indicates this. This problem isn't solved until now in the 7.0er EAP (i can see this because the CPU load is as high as in the 6er release).

My wish at Jetbrains is that they should implement an own VB Editor AddIn for Visual Studio. I'm working both with VB and C# and the VB Editor is sluggish even without R#. Most annoying for me is the poor automatic code formatting and the limitation to 100 syntax errors and warnings.

Another wish for the next release is that Jetbrains concentrates more on making the current features stable and support the new language features than on implementing new functionality.

Regards
Klaus

0
Comment actions Permalink

today  i could work on my source without problems until i started to change the scope of some member variables from public to private. It took just a few minutes until an OutOfMemoryException was thrown by R#.

Regards
Klaus

0
Comment actions Permalink

Hi Klaus

I do agree , adding new stuff is great when its adding to a stable situation.

In my mind , V5 to V6 was a big increase in functionality , when V5 was already straining. I am sure most of us would forsake the odd functionality element for a slicker , quicker performance in the iDE

Jet Brains obviously look at the bells and whistles count first.

I have dropped R# altogether now in favour of Visual Assist X which I have used on and off for years , it loses quite a bit of functionality but it hardly shows up as an impedance in the IDE, you get used to the missing bits , and program again !

Sometimes you have to make those types of decision, My Love Hate relationship with R# continues . I would love to use it but it would seem that would mean a hardware upgrade , again not currently on plan

Good Luck

Mike

0

Please sign in to leave a comment.