Resharper 5+ only works intermittently ... any suggestions?

We had a bunch of computers at work running VS2010 with Resharper. In VS2008, Resharper ran slow enough that all the other devs stopped using it ... even those on quad core boxes and 8GB+ of memory. In VS2010, Resharper 5+ starts up great and works fine ... but then within ~4 hours starts to go downhill. We first notice that simple functions like "Find Usages" return bogus results (or nothing), then it slows down considerably, and finally the mouse stops working (while the keyboard becomes extremely slow). Our project isn't huge either - we only have 5 developers who have been working for a year, so I imagine there are far larger projects using 开发者_StackOverflow社区Resharper.

Any suggestions? 4 of the 5 devs on my team have stopped using Resharper altogether, the other is getting ready to. We all have different configurations, computers, and even OS's, but all have similar problems.

Thanks!

Your results don't sound typical. We have a million-line codebase, and although we did have speed problems with 5.1's test runner (as a result of which we've downgraded back to 5.0), we haven't had any problems like what you're describing.

What sort of project are you writing? R# 5.1 had several fixes for ASP.NET and ASP.NET MVC, and I think there were performance fixes in there too (I didn't pay too much attention since we don't do Web development). If you don't mind a slow test runner and you're doing Web development, try upgrading.

Otherwise, I would suggest that you either write up the issues you're seeing in ReSharper's bug tracker, or contact ReSharper support via their "Problem Using ReSharper" contact form. They might be able to be of assistance, and in the case of the slowdowns they might be able to walk you through getting a profile so they can see what's wrong.

According to JetBrains, it's likely a memory issue caused by using Visual Studio (32 bit) on a 64 bit OS (non-Win7). See: http://devnet.jetbrains.net/message/5262347#5262347

The second issue is a probable bug in the Windows code. If you're running a 32-bit application on more than 2 GB of virtual memory, then getting the mouse cursor position fails when you allocate memory above the first two gigs. Visual Studio is a 32-bit process and, when run on a 64-bit OS, can access something about 3.5 GB of memory. WPF uses GetCursorPos to see where you clicked. Sometimes it allocates memory below 2GB, sometimes above. In the latter case, you lose. Mouse clicks, that is. We were experiencing these problems on VS 2008 as well, but there's just so little WPF code, and other things would not usually rely on getting the mouse position explicitly.

Until you can upgrade to win 7, the workarounds I've found include

• Hit the ALT key. This seems to allow you to click, but you pretty much have to keep hitting it any time you switch windows
• Restart visual studio
• Disable resharper