ReSharper 4.1 issue

I have a project consisting of about 4,000 lines of code in one class that
is causing some really bizarre issues with ReSharper 4.1. One of the methods
has a variable named W that could be moved into an inner block to reduce
scope. When I move the cursor to that variable, Visual Studio 2008 throws up
an hourglass icon for several seconds, I then see a dialog appear and
disappear (so fast I can't even tell what's on the dialog), and then the
process repeats indefinitely. The only way to make it stop is to click
somewhere outside the variable name and wait for the dialog to
appear/disappear. Yes, this is really odd and it continues to happen even
after I close Visual Studio 2008, delete ReSharper's local and global
caches, and restart Visual Studio 2008. If I disable ReSharper it works
fine.

I attached windbg to the devenv.exe process while this was happening and
noticed a significant number of exceptions flying across the screen. It
looks almost as if ReSharper is catching an exception, throwing up a dialog,
clearing the dialog, then trying again recursively.

I captured a memory dump of devenv.exe while this was happening (about 640
megabytes) and uploaded it to my public folder in Dropbox if it helps. Let
me know if you want it and I'll send a link to the memory dump via private
email.


1 comment

Hello Lothan,

Please, send the dump to me: orangy at jetbrains com
Thanks!

Sincerely,
Ilya Ryzhenkov

JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


L> I have a project consisting of about 4,000 lines of code in one class
L> that is causing some really bizarre issues with ReSharper 4.1. One of
L> the methods has a variable named W that could be moved into an inner
L> block to reduce scope. When I move the cursor to that variable,
L> Visual Studio 2008 throws up an hourglass icon for several seconds, I
L> then see a dialog appear and disappear (so fast I can't even tell
L> what's on the dialog), and then the process repeats indefinitely. The
L> only way to make it stop is to click somewhere outside the variable
L> name and wait for the dialog to appear/disappear. Yes, this is really
L> odd and it continues to happen even after I close Visual Studio 2008,
L> delete ReSharper's local and global caches, and restart Visual Studio
L> 2008. If I disable ReSharper it works fine.
L>
L> I attached windbg to the devenv.exe process while this was happening
L> and noticed a significant number of exceptions flying across the
L> screen. It looks almost as if ReSharper is catching an exception,
L> throwing up a dialog, clearing the dialog, then trying again
L> recursively.
L>
L> I captured a memory dump of devenv.exe while this was happening
L> (about 640 megabytes) and uploaded it to my public folder in Dropbox
L> if it helps. Let me know if you want it and I'll send a link to the
L> memory dump via private email.
L>


0

Please sign in to leave a comment.