Forum member
LawrenceShort
9 posts
Posts by LawrenceShort
-
NCRUNCH 3.28 - High memory usage, frequent System.OurOfMemoryExceptions
After applying the change to the Test Processes architecture to be x64 we now no longer get the OutOfMemory exceptions which is great. We're going to have to look at what we can do with the developer machines to make them work properly with NCrunch, however we seem to have surmounted the issue in t…
20 Nov 2019 18:27 UTC
-
NCRUNCH 3.28 - High memory usage, frequent System.OurOfMemoryExceptions
Great, thanks for the help so far.
20 Nov 2019 12:48 UTC
-
NCRUNCH 3.28 - High memory usage, frequent System.OurOfMemoryExceptions
The problem we are receiving with NCrunch restarting all tests from the beginning every time we restart a machine, could this be caused by not having the memory available to load up the code coverage data?
20 Nov 2019 09:55 UTC
-
NCRUNCH 3.28 - High memory usage, frequent System.OurOfMemoryExceptions
Hi Remco, That's where I was heading with my assumptions. I've been looking at the CI build as this is the area that is really hampering our process and have found that if I turn off the InstrumentOutputAssembly setting then the console tools memory usage drops considerably. Which allows the Test…
20 Nov 2019 09:44 UTC
-
NCRUNCH 3.28 - High memory usage, frequent System.OurOfMemoryExceptions
Unfortunately removing the trace output hasn't resolved the issue.
19 Nov 2019 09:26 UTC
-
NCRUNCH 3.28 - High memory usage, frequent System.OurOfMemoryExceptions
Hi Remco, The bulk of the memory consumption is in the nCrunch.EngineHost462.x64.exe process. The BuildHost and TestHost processes do not appear to be causing an issue. Another, less common, exception is a Map.FileOfView error Solution details ----------------------------- * .Net Framwork 4…
19 Nov 2019 09:19 UTC
-
NCRUNCH 3.28 - High memory usage, frequent System.OurOfMemoryExceptions
Something else I've noticed is that restarting a developer machine tends to start NCrunch off from the beginning again, even if it is set to run impacted tests only.
18 Nov 2019 17:07 UTC
-
NCRUNCH 3.28 - High memory usage, frequent System.OurOfMemoryExceptions
Another side note, our tests tend to run at about 1.5 sec per test. I believe this is to do with the fact that we're running the whole stack and that our DI container (castle.windsor) is scanning the assemblies to load all the objects it can find that have an interface for each test instance. Could …
18 Nov 2019 17:00 UTC
-
NCRUNCH 3.28 - High memory usage, frequent System.OurOfMemoryExceptions
Hi, We're using NCrunch as part of our development and CI process. We're experiencing a high number of System.OutOfMemoryExceptions and quite considerable performance degradation. The NCrunch version we're using is 3.28. When running NCrunch will run up to the upper limit of our memory and …
18 Nov 2019 16:57 UTC