ReSharper 2.5.2 died

I am in the middle of converting an old Visual C application and mistakenly pasted perhaps 100 lines of C code into the C# project. The bad news is that ReSharper 2.5.2 is totally freaking out and is throwing a continuous stream of out of memory exceptions and is currently using 624.7MB (devenv.exe is 988MB). I posted the exception to JIRA, but I would like to be able to kill ReSharper without killing Visual Studio 2005. The problem is that apparently either Visual Studio 2005 or ReSharper (not sure which) ignores the option to unload (e.g. I can go into Add-In Manager and uncheck ReSharper until I'm blue in the face, but it stays checked). I suspect this is a bug in Visual Studio 2005 that Microsoft continues to ignore.

Whatever the case, is there perhaps some way ReSharper can recognize that it's falling on its face (literally) and shut itself down gracefully without taking over the entire Visual Studio session?

Attachment not added (content type not allowed): "att1.html"

3 comments
Comment actions Permalink

Hello Lothan,

you can workaround the bug with not persisting disabled state of ReSharper
2.x in Visual Studio by manually resetting the registry value
HKLM(HKCU)\Software\Microsoft\VisualStudio\8.0\AddIns\ReSharperAddIn25[LoadBehavior]
to zero. Concerning your proposal that
ReSharper could recognize that it is dying, I think it's quite difficult
to find an appropriate criteria for this. For instance, an out of memory
exception may or may not be fatal for the whole process. Could you please
clarify: do ReSharper exceptions eventually lead to VS crash?


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


I am in the middle of converting an old Visual C application and
mistakenly pasted perhaps 100 lines of C code into the C# project. The
bad news is that ReSharper 2.5.2 is totally freaking out and is
throwing a continuous stream of out of memory exceptions and is
currently using 624.7MB (devenv.exe is 988MB). I posted the exception
to JIRA, but I would like to be able to kill ReSharper without killing
Visual Studio 2005. The problem is that apparently either Visual
Studio 2005 or ReSharper (not sure which) ignores the option to unload
(e.g. I can go into Add-In Manager and uncheck ReSharper until I'm
blue in the face, but it stays checked). I suspect this is a bug in
Visual Studio 2005 that Microsoft continues to ignore.

Whatever the case, is there perhaps some way ReSharper can recognize
that it's falling on its face (literally) and shut itself down
gracefully without taking over the entire Visual Studio session?



0
Comment actions Permalink

This is a good question. What happened is that ReSharper's memory usage
suddenly skyrocketed and it threw up an OutOfMemoryException dialog. I
submitted the information to JIRA and the Visual Studio 2005 screen turned
completely black. Within a few minutes, a pair of these dialogs would pop up
back-to back. I cleared the dialogs, the screen went black, and then another
pair of dialogs popped up one almost immediately after the other. This kept
up for about 20 minutes until I finally killed devenv.exe from Task Manager.
I can't say that ReSharper actually crashed per se, but it wouldn't allow me
to do anything in Visual Studio before I killed the process. What's funny is
that when I restarted Visual Studio and opened the project, all the code was
still there (including all the funky C code) and ReSharper was idling with
about 200MB memory usage.


"Dmitry Shaporenkov" <dsha@jetbrains.com> wrote in message
news:c8a8945d18848c96fece0347cc3@news.intellij.net...

Hello Lothan,

>

you can workaround the bug with not persisting disabled state of ReSharper
2.x in Visual Studio by manually resetting the registry value
HKLM(HKCU)\Software\Microsoft\VisualStudio\8.0\AddIns\ReSharperAddIn25[LoadBehavior]
to zero. Concerning your proposal that
ReSharper could recognize that it is dying, I think it's quite difficult
to find an appropriate criteria for this. For instance, an out of memory
exception may or may not be fatal for the whole process. Could you please
clarify: do ReSharper exceptions eventually lead to VS crash?

>
>

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

>
>
>
>> I am in the middle of converting an old Visual C application and
>> mistakenly pasted perhaps 100 lines of C code into the C# project. The
>> bad news is that ReSharper 2.5.2 is totally freaking out and is
>> throwing a continuous stream of out of memory exceptions and is
>> currently using 624.7MB (devenv.exe is 988MB). I posted the exception
>> to JIRA, but I would like to be able to kill ReSharper without killing
>> Visual Studio 2005. The problem is that apparently either Visual
>> Studio 2005 or ReSharper (not sure which) ignores the option to unload
>> (e.g. I can go into Add-In Manager and uncheck ReSharper until I'm
>> blue in the face, but it stays checked). I suspect this is a bug in
>> Visual Studio 2005 that Microsoft continues to ignore.
>>
>> Whatever the case, is there perhaps some way ReSharper can recognize
>> that it's falling on its face (literally) and shut itself down
>> gracefully without taking over the entire Visual Studio session?
>>
>



0
Comment actions Permalink

Dmitry-

Over the last couple days we have really noticed similar major memory issues to what Lothan has experienced. Suddenly, R# memory usage will start climbing to 400-600MB even when I am not doing anything. Only restarted my machine seems to bring it back to a range of 100-200 for a while. I am not sure what we could have added to our projects to cause this.

It seems like 2.5 fixed some memory issues present in 2.0, but in 2.5.2 it seems like we are seeing a whole new set of memory issues. Before the last couple days, restarting once or twice a day fixed the problem.

Thanks,
Steve

0

Please sign in to leave a comment.