description

When I run stylecop from visual studio on a managed project within a large solution containing many native projects and a few managed projects, it frosts and eventually kills studio with the following message:

"Microsoft Visual Studio has encountered a problem and needs to close. This may have been caused by low virtual memory levels that were detected prior to closing. Would you like help troubleshooting this problem?"

I've been observing this behavior since at least 4.7.6, though it may have been introduced sooner. I did not observe this behavior in 4.3.2.1.

It not not unique to the project. If I perform a stylecop analysis on any managed project within the large solution, the failure mechanism is the same. Typically the output window will display Pass 1 for nothing or for three or four files before the memory usage explodes. If I run stylecop on a project in a smaller, exclusively managed solution on any project, it works fine.

Sign in to add a comment or to set email notifications