Tests discovery uses ALL memory available, without running tests

Latest , Xunit, dotnet framework as Target project.

Just test discovery (opening test window) causes VS to use all memory available (with freeze and crash at the end)

Latest VS, Latest NCrunch.

I ignored test assembly completelly in Nrunch settings, but after enabling Ncrunch same issue, all memory gone, VS crashed. looks like recursive calls somewhere.



DELETING
v3.ncrunchsolution and .ncrunchsolution.user

HELPED.

Should i provide those files?

Hi, thanks for sharing this issue.

Can you confirm which physical process is responsible for the memory overrun? Task manager tends to aggregate memory usage for the entire tree, but there are many processes involved in an NCrunch session. If you expand the tree, it should be possible to see which one(s) are eating all the memory.

[img]null[/img]devenv.

Not possible to paste picture here.

on the picture i have devenv 30GB.

I encountered that issue already previously.

Fixed by remove ncrunchsolution files. "v3.ncrunchsolution"
"ncrunchsolution.user"


It was not because of TEST run, no tests were running, i even tried unload+disable test assembly in ncrunch+vs configuration.
It feels like happened because nrcunch tried to "discover" tests.


Removed files attached here, should I play around with them to understand where the issue is?

<SolutionConfiguration>
<Settings>
<AllowParallelTestExecution>True</AllowParallelTestExecution>
<HotSpotsLineExclusionList />
<SolutionConfigured>True</SolutionConfigured>
</Settings>
</SolutionConfiguration>

<SolutionConfiguration>
<Settings>
<AutoEnable>True</AutoEnable>
<CurrentEngineMode>Run UnitTests automatically [Global]</CurrentEngineMode>
<HotSpotsTreeShowExcludedComponents>True</HotSpotsTreeShowExcludedComponents>
<HotSpotsWindowSplitterDistance>29.8928909301758%</HotSpotsWindowSplitterDistance>
<ProcessingQueueSplitterDistance>49.9349784851074%</ProcessingQueueSplitterDistance>
<StatusIndicatorSplitterDistance>15%</StatusIndicatorSplitterDistance>
<TestListTreeLayout>
<Column>
<Name>TestFriendlyName</Name>
<Width>690</Width>
</Column>
<Column>
<Name>ExecutionTime</Name>
<Width>111</Width>
</Column>
</TestListTreeLayout>
<TestsWindowMenuOptions>
<VerticalSplitMenuOption>true</VerticalSplitMenuOption>
<ShowPassingTestsMenuOption>true</ShowPassingTestsMenuOption>
<ShowFailingTestsMenuOption>true</ShowFailingTestsMenuOption>
<ShowUnexecutedTestsMenuOption>true</ShowUnexecutedTestsMenuOption>
<ShowIgnoredTestsMenuOption>true</ShowIgnoredTestsMenuOption>
</TestsWindowMenuOptions>
<TestsWindowSplitterDistance>52.4256629943848%</TestsWindowSplitterDistance>
<TestsWindowTreeLayout>
<Column>
<Name>Name</Name>
<Width>809</Width>
</Column>
<Column>
<Name>Status</Name>
<Width>18</Width>
</Column>
<Column>
<Name>LastExecutionTime</Name>
<Width>197</Width>
</Column>
<Column>
<Name>GridNode</Name>
<Width>179</Width>
</Column>
</TestsWindowTreeLayout>
<TestsWindowTreeSortOrder>
<Sort>
<Name>Name</Name>
<Order>Ascending</Order>
</Sort>
</TestsWindowTreeSortOrder>
</Settings>
</SolutionConfiguration>

Thanks for these extra details.

I think this was caused by some kind of display issue. It may be related to the saved UI layouts in the config files. If the problem is no longer bothering you, I'm happy to leave this be unless it appears for you again.

I can try discover more, if you interested to fix it.