Ported from dotnet/roslyn-analyzers#1503
@chillryan
I've reported this issue through the visual studio feedback tool see link but figured I'd try my chances posting here.
I'm using the Code Analysis 2017 extension for VS 2017 15.5. In looking at the stack trace, I can only assume that since the extension is running inside the devenv process, when its analysis a loaded solution, it hits the OOM.
Since I've hit this situation a very frequent basis, I've disabled solution analysis for C# projects hoping that will help. I'll report back here if there are any changes or comment on the visual studio feedback link posted prior.
Ported from dotnet/roslyn-analyzers#1503
@chillryan
I've reported this issue through the visual studio feedback tool see link but figured I'd try my chances posting here.
I'm using the Code Analysis 2017 extension for VS 2017 15.5. In looking at the stack trace, I can only assume that since the extension is running inside the devenv process, when its analysis a loaded solution, it hits the OOM.
Since I've hit this situation a very frequent basis, I've disabled solution analysis for C# projects hoping that will help. I'll report back here if there are any changes or comment on the visual studio feedback link posted prior.