Loss of local variable values while debugging

Hi,

I've been using ReSharper for C++ (2016.1.2). I've run into an issue where after running for a certain amount of time I suddenly lose the ability to see the values of local variables when I'm debugging. I've seen this in both Visual Studio 2013 and Visual Studio 2015 with Resharper running. My only recourse when this happens is to restart visual studio. I've noticed this behavior even when I have solution wide analysis turned off, though it seems to occur more frequently when I have it turned on. Is there an option I could possibly turn off to prevent this from happening, or is this a known issue that will be fixed at some point? Thanks.

7 comments
Comment actions Permalink

Hello Martin,

As far as I know, ReSharper does not affect debugging in any way, and we have never heard about the problem that you describe. Could you please make sure it's ReSharper that's causing the issue? You can suspend ReSharper for some time via Visual Studio options, and check if the problem reproduces with ReSharper disabled.

0
Comment actions Permalink

Yes, I have verified that it is ReSharper causing the problem. When I suspend it, I never run into this issue, but when I have it enabled for more than 20 or 30 minutes it happens very consistently. If there's any way I can provide you more information please let me know.

0
Comment actions Permalink

Martin, can you please also check how much memory does the Visual Studio process consume when this problem occurs? We believe that when VS consumes more than 2GB, some COM objects inside VS that participate in debug might not behave correctly, so we'd like to check whether the memory pressure is the source of the problem.

0
Comment actions Permalink

Hi Igor,

Yes, I have confirmed that VS is using more than 2GB of memory when this occurs, it seems to hover around 2.3GB while solution analysis is running. It eventually cleans itself up to around 1.5GB, but it seems as though once this behavior begins it never goes away until I restart Visual Studio. The solution I am working in is very large so the memory usage does not come as a huge surprise.

0
Comment actions Permalink

If possible, could you take and send us a memory snapshot using the instructions at https://confluence.jetbrains.com/display/ReSharper/ReSharper+Profiling+Instructions, so we can take a look at how memory is consumed? Also, is this pure C++ solution or does it also have C# code? If your solution contains significant amount of C# code, disabling solution wide analysis can help somewhat since it's known to aggressively use memory.

0
Comment actions Permalink

I wanted to note that I just downloaded an eval copy of the product for VS2012 and I see the same thing - local vars are not visible when debugging, analysis is running, and process size > 2GB.  Knowing what's happening makes it better, but this is not ideal.

0
Comment actions Permalink

Hello Steve,

You can try to reduce ReSharper's memory usage by excluding files that you're not interested in from indexing using the Third-Party Code options page (see https://www.jetbrains.com/help/resharper/2017.1/Reference_Options_Code_Editing_Third_Party_Code.html  for details).

Thanks!

0

Please sign in to leave a comment.