Anybody else encountering any issues with the latest version of NCrunch?

During initialization of NCrunch Visual Studio starts eating up lots of memory (over 2.5 GB) and becomes unresponsive. This takes minutes and sometimes causes VS to even crash. The problem occurs before the tests are run (I set them all to be started manually). Even when it succeeds to initialize, the problem repeats whenever I change the code. It seems to me that it is caused during build. I tried deleting the cache, disabling and reenabling NCrunch, restarting Windows, but nothing helped.

After I uninstalled the latest version and installed NCrunch v2.5, the problems went away completely. During NCrunch initialization the Visual Studio memory footprint hardly changes. Visual Studio also remains responsive during code changes and general "crunching".

Today I updated NCrunch to V2.6 again, but I couldn't reproduce the above described issue, no matter how hard I tried, neither with the solution I worked on yesterday (even if I reverted it to the same state), nor with any of my other solutions I used NCrunch with in the past.

I plan to continue development on that same solution most of the day tomorrow and I'll definitely let you know if the issue reappears.

Sorry for the false alert, as it currently seems, but it really seemed connected to the new release of NCrunch, since I haven't changed anything else on my machine recently, including since yesterday's issues.

I managed to reproduce the issue again. It seems to be related to the NCrunch Tests window. The huge memory consumption only occurs when this window is visible and has a width below cca. 700 pixels. It happens even if I don't change the code at all, but only make the window narrower. Once NCrunch manages to render it again, the memory footprint and CPU usage get down again, but increase as soon as I change something in the code. I can't test this for long because in a few attempts at maximum, Visual Studio crashes.

I have now reorganized my windows a bit to keep NCrunch Tests window wider and avoid the issue. I'll continue working like that for the rest of the day and let you know if the issue still comes up.

On an unrelated note: in the previous version compilation errors were displayed in the bottom pane of NCrunch Tests window when the project with the failed build was selected in the list above. In the latest version the bottom pane remains empty if this is the case. Is this a feature or a bug?

It happens, when I resize the window below a certain width. If I keep it open like that it seems to be happening every time, the window is being re-rendered. I followed your advice and turned off all the filters, so that there was nothing in the list; it didn't happen then.

I also enabled logging to Output window. Every time the memory consumption spiked, there was an OutOfMemoryException logged in the Output window, unless Visual Studio crashed. Here are two of them:

[10:53:16.5355-UI-1] ERROR (Internal): System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at System.Collections.Generic.LinkedList`1.AddAfter(LinkedListNode`1 node, T value)
at NCrunch.VSAddIn.UI.TextDisplayControl.SplitTextContent..ctor(String content, Int32 maxLineLength, IList`1 hyperlinks)
at NCrunch.VSAddIn.UI.TextDisplayControl.TextDisplay.#=qGSGTWkQNY2kpk80EcsPwNpD24mCxC49a98wrR3IR8mE=()
at NCrunch.VSAddIn.UI.TextDisplayControl.TextDisplay.#=qGn0Nyw$MZfgpGdRkg_$P3Q==()
at nCrunch.Common.ErrorHandler.DoWithErrorHandling(Action action, Object context)

[11:01:26.5325-UI-1] ERROR (Internal): System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at System.Collections.Generic.LinkedList`1.AddAfter(LinkedListNode`1 node, T value)
at NCrunch.VSAddIn.UI.TextDisplayControl.SplitTextContent..ctor(String content, Int32 maxLineLength, IList`1 hyperlinks)
at NCrunch.VSAddIn.UI.TextDisplayControl.TextDisplay.#=qGSGTWkQNY2kpk80EcsPwNpD24mCxC49a98wrR3IR8mE=()
at NCrunch.VSAddIn.UI.TextDisplayControl.TextDisplay.SetContent(String content, IList`1 hyperlinks)
at nCrunch.VSAddIn.UI.TestTree.LinkedOutputText.ApplyToTextDisplay(TextDisplay textDisplay)
at nCrunch.VSAddIn.UI.TestTree.TestsWindow.#=q1jsKORUTV365ycPrrX_UpWGVN_lGVMpwm3od7OdPDVE=()
at nCrunch.VSAddIn.UI.TestTree.TestsWindow.#=qyTUshAyxncThR5sVu_CfUvZSa0jDRO5GkqDI8KFXyoU=()
at nCrunch.VSAddIn.UI.TestTree.TestsWindow.#=qXh4RBEdbhNe$xdZXbUrMWyheqCowogzjwwMxRyM6I_s=(Action #=q2vPU17HO5WTRRANNRxBmaw==)

Strangely enough, the window still seemed to be properly rendered after this exception.

Regarding the build errors: they are logged to the output window and they are displayed in the Processing Queue window. They just don't show up in the NCrunch Tests window. but there are no exceptions logged when I have it open wide enough and build errors are being logged. Could I somehow turned that off? It's not that much of a problem though, since build errors are listed in Visual Studio's Error List window anyway.

I created a new solution from the unit test template in VS which only includes a single empty unit test. The problem was still there.

In the meantime I noticed that the Test window text output pane never displays any text (even with large enough width): not only there's no build errors, there are also no test failures or console output. The same goes for the empty test solution I created from the template.

I usually have the text ouput pane at the bottom, but it makes no difference if I put it on the right. As soon as it (not the whole Tests windows) gets below a certain width, the memory spikes occur.

I also tried installing the latest version of NCrunch on my laptop. At first it seemed to work ok (displayed text in output pane as expected, even with the window being really narrow). I then tried connecting the laptop to a second screen and the issue started occuring there as well. It might not be directly related to that, since I now have the same issue on my laptop as well, even when it is not connected to an external display.

Right, I wonder if this is related to the new font setting that was introduced in 2.6.

Can you let me know what the 'Text output font' is set to under your global configuration? And whether changing it makes any difference?

Also, are you running in standard DPI?

Gotcha. That will be it then. NCrunch is reading the font size from the config file using the current culture, and storing it using the invariant culture. It seems that 8.25 returns 825 when read with a different culture. This messes with the text output slicing causing the text pane to gobble insane amounts of memory. The high font size will also make all text in this window invisible.

I'm preparing a fix now for this issue. It's very serious so I will release it as 2.7. Sorry for the trouble, I'll update the download page soon.

I purged all of my NCrunch configuration files and repeated the original replication steps and everything is working perfectly now. Thanks for the quick turn around.

Thanks for the confirmation. I've updated 2.7 with a minor build (2.7.0.3) that contains a change to automatically reset the font size if it's higher than 600. This should correct the issue for unsuspecting users.