[230] Find Usaged 100% CPU

Greetings everyone,

My team has observed various "hangs" with Find Usages since we've been using ReSharper early access releases (since build #227, I think). It usually happens when clicking around the tree displayed in the Find Usages window, but it's also happened when we've tried to filter the results by get/set/both on properties.

Recently, we discovered that if we click the Show Desktop shortcut (which minimizes all windows) in our Quick Launch bar, ReSharper is no longer hung as shown in the Windows Task Manager. We can then restore the VS.NET 2003 window and continue with our work. We've reproduced this on a few different machines. Note that we never received an exception with this before discovering this work around. Either VS.NET eventually became usable again, or, more likely, we grew tired of waiting and terminated the devenv.exe process.

We haven't installed build #243 yet. If anything is differnt with it, we'll try to post our results.

Regards,
Craig

Message was edited by:
Craig Demyanovich

Hello Craig,

if this problem is repeatable for you in the latest build, could you please
try to attach the debugger to devenv.exe
when it appears to be hung and capture stack traces? Thanks in advance.


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

Greetings everyone,

My team has observed various "hangs" with Find Usages since we've been
using ReSharper early access releases (since build #227, I think). It
usually happens when clicking around the tree displayed in the Find
Usages window, but it's also happened when we've tried to filter the
results by get/set/both on properties.

Recently, we discovered that if we click the Show Desktop shortcut
(which minimizes all windows) in our Quick Launch bar, ReSharper is no
longer hung as shown in the Windows Task Manager. We can then restore
the VS.NET 2003 window and continue with our work. We've reproduced
this on a few different machines. Note that we've never received an
exception with this. Either VS.NET eventually becomes usable again,
or, more likely, we grow tired of waiting and terminate the devenv.exe
process.

We haven't installed build #243 yet. If anything is differnt with it,
we'll try to post our results.

Regards,
Craig

Hi Dimitry,

With bild #243, I was able to make VS.NET hang by clicking around a bunch in the Find Usages window, which was docked at the bottom of my VS.NET window. It took much more clicking around to make it hang this time, though.

I did attach a debugger to the hung devenv.exe process. The only way I could get a call stack was to enable a setting in the call stack tab named "Include Calls To/From Other Threads." Furthermore, the only item in the stack trace is:

jetbrains.resharper.shell.dll!JetBrains.ReSharper.Shell.SocketManager.PortListenerThread.Run() Line 131 + 0xe bytes C#

I hope this helps.

Regards,
Craig

Hello Craig,

please inspect all threads using the 'Threads' debugger window. Also make
sure that the option
'Enable Just My Code' is disabled. Thanks.


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

Hi Dimitry,

With bild #243, I was able to make VS.NET hang by clicking around a
bunch in the Find Usages window, which was docked at the bottom of my
VS.NET window. It took much more clicking around to make it hang this
time, though.

I did attach a debugger to the hung devenv.exe process. The only way I
could get a call stack was to enable a setting in the call stack tab
named "Include Calls To/From Other Threads." Furthermore, the only
item in the stack trace is:

jetbrains.resharper.shell.dll!JetBrains.ReSharper.Shell.SocketManager.
PortListenerThread.Run() Line 131 + 0xe bytes C#

I hope this helps.

Regards,
Craig