RefactoringEssentials
RefactoringEssentials copied to clipboard
Visual Stupio stops responding for a long time after a short while at cold start
When Refactoing Essentials is enabled and I make a VS cold start (that is, it has been a long time since the last time and it's not cached and pre-fetched and all), after a minute or two of work VS stops responding. I have to wait at least 3 minutes until it responds again. If I kill it while it's not responding and start it again, the same thing happens. Apparently RE needs to finish some process and if that process is killed while not complete, it starts it again next time. All of this occurs each time and does not if RE is turned off.
Does it happen with a particularly big solution or is there anything else that might be special about it? I've tried some of the big solutions we used for testing of previous VS performance problems, but I've never seen a complete hanging.
BTW: RE analyzers are completely stateless, they only analyze pieces of code as triggered by VS. RE doesn't actively cache anything. All control is on Roslyn side.
It happens most often with https://github.com/mono/CppSharp . It has a large C++ (both regular and CLI) part. In case you'd like to test, please note that there's no static solution file, you have to generate it by running
@Rpinski have you been able to check this solution? If not, can I help?
I've been able to generate the solution and open it, but unfortunately I didn't see VS hanging at all. No performance issues, only 400-500 MB RAM consumption.
Maybe I'm still missing some prerequisite, because the solution doesn't compile with error messages like "The command "D:\Andreas\projekte\RefactoringEssentials_TestProjects\CppSharp-master\build\vs2015\lib\Debug_x64\Common.Gen.exe" exited with code 9009.
BTW: Is RE the only code analyzer extension you have installed?
@Rpinski please ignore those errors, you don't need to compile it and I assure you you have no missing dependencies. About code analysis, I only use RE.
Ok, but do you have only 42 analyzer warnings and 23 messages, too?
I have 69 warnings and 0 messages in "Error List". I assume, however, that this is not what you mean. Is there some other output I should check?