Log chunk is too large

Hello,

I had recently updated to v4.7.5 and upon doing so started having one of my test project's fail with the TargetInvocationException below after processing about 1/3 of the tests. It didn't seem to be a resource issue, or at least I didn't notice anything in Task Manager. Thanks

An error occurred while analysing this project after it was built: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Exception: Log chunk is too large (max size 16777215)
at nCrunch.Common.Logging.SharedMemoryLogBuffer.Write(LogVerbosity verbosity, String value)
at nCrunch.Module.NUnit3.Integration.NUnit3DiscoveryListener.RaiseCallbackEvent(String eventArgument)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark)
at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
at System.Activator.CreateInstance(Type type, Object[] args)
at nCrunch.Common.PerformanceTracking.PerfTracker.TrackActivity(String name, Action activity)
at nCrunch.Module.NUnit3.Integration.NUnit3FrameworkInteractor.ExploreTests()
at nCrunch.TestExecution.TestFinder. . ()
at nCrunch.Common.PerformanceTracking.PerfTracker.TrackActivity(String name, Action activity)
at nCrunch.TestExecution.TestFinder. . ()
at nCrunch.Common.PerformanceTracking.PerfTracker.TrackActivity(String name, Action activity)
at nCrunch.TestExecution.TestFinder.FindTestsForFrameworks(ReflectedAssembly assembly, FilePath assemblyFilePath, IList`1 referencedAssemblyFilePaths, DescribedTestFrameworkDiscoverer[] describedDiscoverers, ComponentUniqueName testComponentUniqueName, PlatformType platformType, DynamicProxy[] dynamicProxies)
at nCrunch.TestExecution.RemoteTaskRunner.AnalyseAssembly(DescribedTestFrameworkDiscoverer[] applicableFrameworks, ComponentUniqueName testComponentUniqueName, PerfTracker perfTracker, TaskLogId taskLogId)

Hi, thanks for sharing this issue. This is caused by the new logging system. It seems to be possible for the NUnit output to be extremely large for some projects.

Could you try the build below to see if this solves the issue for you?

NCrunch_Console_4.8.0.2.msi
NCrunch_Console_4.8.0.2.zip
NCrunch_GridNodeServer_4.8.0.2.msi
NCrunch_GridNodeServer_4.8.0.2.zip
NCrunch_LicenseServer_4.8.0.2.zip
NCrunch_VS2008_4.8.0.2.msi
NCrunch_VS2010_4.8.0.2.msi
NCrunch_VS2010_4.8.0.2.zip
NCrunch_VS2012_4.8.0.2.msi
NCrunch_VS2012_4.8.0.2.zip
NCrunch_VS2013_4.8.0.2.msi
NCrunch_VS2013_4.8.0.2.zip
NCrunch_VS2015_4.8.0.2.msi
NCrunch_VS2015_4.8.0.2.msi.7z
NCrunch_VS2015_4.8.0.2.zip
NCrunch_VS2017_4.8.0.2.msi
NCrunch_VS2017_4.8.0.2.msi.7z
NCrunch_VS2017_4.8.0.2.zip
NCrunch_VS2019_4.8.0.2.msi
NCrunch_VS2019_4.8.0.2.msi.7z
NCrunch_VS2019_4.8.0.2.zip

Yes the issue no longer occurred after installing this version. Thanks.