R# 2016.3.2 has a memory bug after a build
R# 2016.3.2 has a memory leak bug. Several member of my development team, along with myself, have observed this issue. We all recently upgraded from R# 10.0.2 where we did not experience this problem. I am having trouble separating all of the variables but it seems like the problem is triggered by running a project. I do not have SWA enabled, we are using VS2015 Update 3 with C#
1. Run the project.
2. In a large file (more than 20,000 lines) perform some code refactorings for the whole file (I change variables to use 'var' but the issue is not limited to that particular refactoring, just about anything seems to work).
3. The amount RAM increase rapidly up to some large number (say 1.5 GB)
4. Garbage collection should run and reduce the RAM to some smaller number (say 1.0 GB)
5. The amount will continue to rapidly increase (say 1.55 GB)
6. GC will run again but it will always be a little bit larger than the previous amount.
7. Steps 5, 6 will continue to occur until VS2015 crashes.
I have also noticed that while all of this is going (after my build) on 1-2 of my 8 logical processors will be continuously used, about 15-25%
The below image is the amount of RAM used by R# while I was not making changes in VS.
Please sign in to leave a comment.
Hello Thomas,
Please follow these steps https://resharper-support.jetbrains.com/hc/en-us/articles/115000265844 to collect a memory snapshot when the amount of allocated RAM increases up to huge numbers.
Thanks!
I was unable to use the "Report a problem" feature to submit a snapshot. I uploaded the files via HTTP with the filename "ReSharperMemoryIssue.7z". There are 3 memory snapshots in that file. Feel free to contact me if there are questions or more info is needed.
I wanted to let you know that 2017.1 has the same issue and memory usage is high even without building as reported in my first post.