Hi

There are a number of threads about this problem. Indeed its seems the 6.1 EAP was pushed forward to at least show some alliviation of the problem.( the processing files issue)

I agree Just Code looks very promising , the guys at Telerik were very kind a while back and gave out free JC licenses to users who recommended their Just Decompile product .

I have had so many issues with R# that I have eventually had to uninstall on my production PC where I handle big solutions, including Db Projects. I am using a combination of Just Code and Whole Tomato's Visual Assist X (To make up for a lack of intellesense help in JC -- any time now they claim). They seem to lay well together.

I do appreciate trouble shooting these issues is difficult , but Jet Brains response always seems to be to send snapshots, videos , sample code etc

Its almost as if can't actually believe its their issue.

I am realtively new to R# (3 yrs) but I do smart at paying the initial V5 first licesne and then a further $ 120 for an upgrade not long after and it still limps along

My confusion is that I bought a product and I expect it to work . Sometimes I think its me then comments like yours pop up and give me some confidence to keep nagging Jet Brains.

I have tried most of the add ins over the years , and have this love hate relationship with R# , it is a superb product with lots of featured BUT , if it kills the IDE to the point of not working properly what use is it. When I uninstall I miss it , when I Install I curse it.

Another issue I don't like is that installing R# BLOCKS Just Code , it just dissaperas , so you can't even have them installed and switch betqween depending on performance needs.

It will stay uninstalled for now , until I get a warmer fuzzier feeling that all has come right.

Just Code is competing pretty well on most fronts , when intellesence appears Jet Brains must watch their market place .

Mike

Hi Andrey

As you can gather there is a  fair amount of frustartion in my reply

I seem to spend most of my time swapping between add ins trying to find the happy medium adding to the frustration.

The bottom line is that when it comes to the final analysis ,  R# is still the most fully featured product out there , and I inevitatbly give up and GO BACK , hence the Love Hate

It doesn't take the frustration away , if anything it makes it worse. I REALLY do want to use R# , please believe that . For all the hunting at near competitors none of em quite make the mark.

But with poor performance it just makes things worse. I am back (as ever) to R# this morning with another vow to perservere ...

WRT the Just Code block ,I appreciate its not deliberate but it is true , it may be courteous to your competitors to investigate why the clash exists and maybe work together to get around it . If for any reason I choose to Use JC instaed of R# , instead of a couple of ticks and a VS restart , its an complete install uninstall cycle, which takes time.

I am using the 6.1.29.21 EAP build currently (is their an better one ? )  and will keep monitoring

The Love Hate Continues

Mike

Hello Mike

     I understand your frustration and I really hope that we will address this problem somehow. At the moment there's build #35 that is very close to release state and that has reduced number of assertions, logging and sensitivity to errors (which in terms should lead to better performance). Could you please install that build and write back in case it doesn't help with these problems? Thank you!

Andrey Serebryansky

Senior Support Engineer

JetBrains, Inc

http://www.jetbrains.com

"Develop with pleasure!"

Hi

Managed to catch the exception , I was just generally editting , not building etc

I had to screen shot as I could copy from the dialog

Hope it points a directions

Mike

I have also an annoying problem with my studio+resharper 6.1.1000.82. Sometimes it does not let me just edit my code. I must wait for a couple of seconds if i want to type a word. I thought first it happens only in some very big cs files ~4000 with a lot of inspection issues. But today i have the same issue in a relative small ~200 lines file with no bulbs. I have used dotTrace from EAP to generate a snapshot. During editing about 5 minutes and make some refactorings, dotTrace has generated a 5,5 Gig! snapshot. I have packed it to 1.8 Gig "bigCs.zip" and uploaded it per ftp to ftp://ftp.intellij.net/.uploads/ like described in http://confluence.jetbrains.net/display/ReSharper/ReSharper+Profiling+Instructions.

This is a .net 4.0 winforms solution with 20 cs projects

Yes, suspending R# helps definitely. But i will experiment with uninstalling of some VS extensions anyway.

Hello Jakub

     We're sorry to hear that you're having such problems with ReSharper. Yes, performance is a common problem and we're doing our best to eliminate as many performance problems as we can (you can see the list of performance problems fixed in ReSharper 6.1 here: http://youtrack.jetbrains.net/issues?q=project%3A+RSRP+%23%7BPerformance+Problem%7D+%23fixed+fix+for%3A+6.1). Have you tried ReSharper 6.1? If yes, do I understand correctly that it didn't work fast enough for you?

Andrey Serebryansky

Senior Support Engineer

JetBrains, Inc

http://www.jetbrains.com

"Develop with pleasure!"

Now to provide a complete opposite repsonse, I use R# with solution analysis on multiple solutions with upwards of 4 visual studios open concurrently.

I never feel like R# impacts the performance of my machine.

My largest solution is only about 50 projects however.

Maybe the real issue is that your team needs to improve how you structure code that it has 150 projects in a solution? Or maybe your business needs to provide you with better hardware to do your job? For reference we develop in Win7 x64 on quad core 3.2ghz xeons with 12GB of ram. Have never in my life seen an OOME from R# since 2008 on a Windows XP machine with only 2GB of ram. If your hardware is crap, well what do you expect.

Those specs are comparable to mine other than the ram being lower. There might be reasons to have 150 projects in the solution, doesn't mean it's correct.

PS @ Andrey

Any move on the issue above , its marked as critical and has been sitting the re since well before Xmas ???

Mike

Giving developers 32bit PCs is just silly. Your company is LITERALLY pissing away money. You're losing time due to your machine not having correct resources, time lost is money lost.

The cost of a PC in comparison to a software developer is measured in hours.

"we shouldn't have to change our ways of working to allow a product (like R#) to work."

That's also a silly statement.

R# is a gigantic database that sits on top of your code, to be able to expect R# to work well when your system has no available memory to host its database because your machine has too little memory and the solution has 150 projects in it (VS itself will probably take 1GB just from that, of your total 3gb if its 32bit).

Making these kinds of statements is like making the argument that SQL server is at fault for queries failing with OOME because the machine hosting it has 1GB of ram and your query is a god query that joins in every single table in the database together.

If anything I WISH R# USED MORE MEMORY. Put more in memory, less on disk, would make everything so much faster.

Maybe Jetbrains should be more strict about the Requirements of the product for it to run smoothly ? especially debug builds.

The latest release build is working pretty good for me.

  Welcome to the corporate world ...

I don't disagree , but while we are small development team (12 of us) in a BIG manufacturer of 15,000 employees , we have a small voice  too. Our prime business is manufacture , not software so our PC's are aimed at one size fits all , at least this time around we got a decent 32 Bit spec PC, up from the email and Word and Excel bashers

Life like that

I too can vouch for those OOM errors going away with the switch to Win7

64-bit.  Even with only 4GB of memory, the problem was alleviated.

Any pressure you can provide to give your developers a 64-bit OS, and more

than 4GB of memory will be effort well spent (and investment for your

company well spent).  The amount of productivity we get back for that small

investment is more than worth it.

"Mike O'Neill"  wrote in message

news:23369969.52821326086015560.JavaMail.devnet@confluence.jetbrains.net...

Welcome to the corporate world ...

I don't disagree , but while we are small development team (12 of us) in a

BIG manufacturer of 15,000 employees , we have a small voice  too. Our prime

business is manufacture , not software so our PC's are aimed at one size

fits all , at least this time around we got a decent 32 Bit spec PC, up from

the email and Word and Excel bashers

Life like that

---

Original message URL: http://devnet.jetbrains.net/message/5448296#5448296

Hi Charles

Thats good (or bad ) to hear , I was beginning to think I was a lone voice out there. We are in the same boat , we have a large legacy app , half in VB ., half in C# . The SQL db project is also enormous.

Its unlikely we will upgrade this app much more , we just keep adding functionality . Its more likely to get replaced.

I find I keep 6.1 running by routinely restrarting VS every couple of hours , its a pain but it saves the crashes. I also reboot my PC daily to make sure I have no memory hang ups anywhere ( . we have new PC with solid state drives so this is no problem , a miniute or so , compared with our old PC's at 10 mins).

I do think that at the moment Jet Brains has abandoned hope on this , there is an incident in their system , since before Xmas which has received Zero attention.

As I have said so many times , R# IS the best tool , but not while it causes grief like this . Its a Love Hate relationship.

My suspicion is that because we shoudl all have super 64 Bit PC  etc with loads of RAM as our friend above comments, thats what they test on . They wouldn't see the pain we suffer.

Maybe some of their developers should Dog Food R# on a 32 Bit 4 Gb PC for a while , they may just wake up

MIke

Hi Andrey

Sorry If I keep harping on ....

At least now there is something definitive said about 32 Win and OOM errors.

If I get this right , in effect you are saying that R#6.1 is not compatible with VS 2010 running under Win 32 if I am to use large solutions. (defifne large ?)

I have been using R# fro 3 years or so and I have never been aware that there is this limitation , is it described anywhere in documentation that I should have read before I bought it ?

I have been using 32 Bit Win for ever , and its unlikely I will change just to be able to use a specific tool, but I would like to have known about the limitation before I spent hard earned cash purchasing something which seems to be destined to cause me problems. Equally in my work environment I have no say over what PC I use , its simply provided.

As you can appreciate , I like the features of R# and I don't think there is anything else out there to come close to it , but while I get either OOM errors or have to restart VS every hour just to work with it , it seems a two edged sword , you can't easily work with or without it . Back to my Love Hate relationship.

I assume this limitation was not there in V5 , should I reinstall V5 maybe , would that help ?

Short of that, do Jet Brains have any suggestion as to what I should do , and more to the point what I should do with what appears to be a redundant product in my environment.

I apologise if this sounds irritating but I am irritated .

Mike

Hello Mike

     This one comes from the File Structure window, so I'd suggest to check if working with this window closed helps to avoid OOM errors. Thank you!

Andrey Serebryansky

Senior Support Engineer

JetBrains, Inc

http://www.jetbrains.com

"Develop with pleasure!"

I am not able to use the 3G switch, as it conflicts with some of the security and HIPAA software on my machine.

Unfortunately that is not true for most of our Borland apps.  They have custom interfaces with a variety of hardware to pirnters, inserters, scanners, bar code readers, etc.  We have tried to run them on x64 a couple of times and it has failed.

I don't see how your comment is relevant to the conversation, but for sake of argument...

Lots of companies have invested in software that only works on the x86 platform.  Many of these applications are expected to live for 5-15 years and possibly longer before replacement.

Now in the case of our company we are slowly porting various applications when they need changes...   Porting old Borland C++ win32 apps to Visual Studio.  We do build new apps for x64, but we still have to support the old.  Unfortunately, these old borland apps do not run on an x64 OS, even when we try x86 mode and we have 100's of these old apps.  So when we can we upgrade them, but until they're al upgrade we're stuck with x86 os.

R# 5 worked fine, R# 6 crashed and died horribly.  Do a search of the forms and you'll see my request to back down to version 5, which went unanswered.

Regardless of your opinion on what a viable development shop should be or have.  There was no indication from JetBrians that upgrading to V6 would require such a drastic change in the development environment.

At this point, the lack of support and the virtol from posters like yourself is just pushing shops similar to the one I work in to other vendors.  You buy a product to solve problems, not create them and R#6 is creating more problems than it solves and changing our entire development environment is not an option.

If that's the size of your solutions, unless there's like 8 billion code files in them, I would say yes R# should work on a 32bit machine. But this could directly relate to the # of visual studios open, the number of other apps running (are virus scanners messing with index files for R# etc)

Nice Debate , I missed it as I was sunbathing !!

While I do not wholly disagree with the resource loss argument from Chris , but after 40 years in a corpoarate world you learn that sometimes we have to live with what we are given and make the best. Debating 32 v 64 bit architecture with an accountant normally has little if any impact . In a dedicated software house the argument may wash  , I am not in that environment we are a FMCG comapany.

I do however take up the previous argument, if R# 6 was going to be so much more demanding that previously maybe warn us before we but it. Finding out when it crashes VS is not really the way to do it.

I do feel a bit agreived by Jet Brains " innocent until proved guilty "  approach they always want to see "proof" before they investigate. We all develop software , or we would be commenting here, and we all know how difficult it can be to root out some lurking performance issues, but Come Clean and admit they may be there maybe ....

I am working on 2 sorts of projects , big complex ones at work , small , hopefully well designed ones at home. The home ones are max 6 structured projects to a solution, and the one I am working on at the moment as my reference point has maybe 30 classes per project. I use this as a reference to see what changes , as this project doesn't. So the complaints based on Monolithic Solutions is not valid.

The real dilemma is that when you look for an alternative to R# , it isn't there . Visual Assist X is brilliant , but only covers 50% of R# . Just Code is good and improving but they seem to not see a need for Intellesence , CodeRush is Just Different....

So we get back to using R# and put up with the issues , but in our case why put up and shut up when we can debate as we are doing . Maybe Jet Brians will comment on this thread sometime , Andrey has commented but , with all due respect, without really joining the debate.

I am rapidly looking towards Visual Assist X and Code Rush Express to provide the best coverage without the memory issues.

Lets see what Jet Brains can come up with

Mike

Hi Bobby

Bit rude advertising competitors BUT ...

Maybe try a demo of Visual Assist X if you haven't already , its a bit C++ Biased and has a few holes in VB  Refactoring but for C# its fine. The Tools like Outliner match R# equally .

its very similar to R# but covers a lot less , and I think is less memory demadning as a consequence. I have used the freebie Coderush Express along side with no issues just to supplemt the shortfalls in Refactoring.

Mike

Hi Andrey

I am sorry if dicussions here hit a sore point , I have given up on R# , I am trying to find something that replaces your functionalty , take it as a complement that this is not easy

If I find a fellow sufferer then so be it

I have been a devoted R# user for years and find it very hard to give it up , but while I cannot use it without VS 2010 crashing what am I to do, I have often used the Love Hat comparison , I lobe the product but I simply cannot live with its foibles , Am I Alone ???

If you find my comments re Jet Brains painful then maybe you should take note of that  and do something about it.

I spent good money upgrading to V6 and I have had nothing but pain since , I had few peoblems with V5 , and even less with with your competitors products

I will stop contributing to this thread if that please you , after all censorship keeps the masses in the dark

GOODBYE , and goodbye to Jet Brains products if thats what you want

Mike