After few days of using 1.39b, nCrunch started to take very long time on "NCrunch engine is initialising". Previously it took several seconds, now it takes several minutes. I've looked into Task manager, and it shows, that devenv.exe fully loads one core, several nCrunch.TaskRunner40.x86.exe are idle (I'm working on a 6 core machine). When nCrunch ended it's initialization, devenv.exe dropped to 0, and taskRunners started to work.
More info:
- When nCrunch is initialising, Queue and Configuration windows are empty.
- I've tried to reinstall nCrunch with devenv.exe /setup (as in: http://forum.ncrunch.net...-in-1-39b.aspx#post1892) but without luck.
- On other machines, nCrunch with same solution works fine.
- I'm not 100% sure, but it may be connected with updating "Productivity Power Tools" to newest version, but after uninstalling PPT nCrunch still doesn't work as before.
- It looks like it's worse, when I'm opening solution by double clicking on .sln, than opening VS and then opening solution.

There's part of the log, where nCrunch was waiting (this time, it was only about a minute - I was opening Visual Studio, and then solution)

[15:27:53.548-BuildTask-26] Unable to find config file.
[15:27:53.548-BuildTask-26] Build was successful for f:\ncrunch\4184\2\Source\InstalSoft\Utils\..\..\..\bin\InstalSoft.Utils.dll
[15:27:53.548-BuildTask-26] Task processing complete for [BuildTask: [SnapshotComponent: InstalSoft.Utils, 4, 31189065], BeingProcessed], processing time: 00:00:00
[15:27:53.548-BuildTask-26] Publishing Event: [#=qU6CMv5fi3VqxV1Hah2HO4ub0$OGid0LFU89e$xAhlI0=:[BuildTask: [SnapshotComponent: InstalSoft.Utils, 4, 31189065], BeingProcessed]]
[15:27:53.548-BuildTask-26] Event [#=qU6CMv5fi3VqxV1Hah2HO4ub0$OGid0LFU89e$xAhlI0=:[BuildTask: [SnapshotComponent: InstalSoft.Utils, 4, 31189065], BeingProcessed]] is being published on thread CoreThread to subscriber: ProcessingQueue.#=qfACt$cJfCa1u3ESIRefJASDJe3c3a9TBCZQga5VQE08=
[15:28:52.1484-Core-14] Publishing Event: [TestDataUpdatedEvent]
[15:28:52.1484-Core-14] Event [TestDataUpdatedEvent] is being published on thread CoreThread to subscriber: StatusIconSynchroniser.#=q0ItZAR5uLMMyOc0Dhv8irw==
[15:28:52.1484-Core-14] Event [TestDataUpdatedEvent] is being published on thread CoreThread to subscriber: CodeCoverageMerger.testDataUpdated
[15:28:52.1484-Core-14] Event [TestDataUpdatedEvent] is being published on thread CoreThread to subscriber: CoverageWatcher.testDataUpdated

PS. it looks, like 'Log to output window' and 'Logging verbosity' settings aren't saved, so I can't send you log from scenario, when I'm opening solution by double click.

Clearing .cache file solved the problem - thanks.

Hi Marqus,

Checking through the log file, it looks like this could be a performance problem that is causing the engine to seize up.

Can you tell me a bit more about the solution/situation you're working in? Particularly I'm interested in:

- A rough number of files/documents you have open in the IDE at one time
- Rough number of lines of code for your solution (the metric shown in the Metrics view would be fine)
- Approx number of projects
- Approx number of tests
- Do you have any areas of your codebase with very high test coverage saturation? (i.e. more than 1000 tests covering individual lines of code)

Thanks for sharing this. None of this looks particularly unusual except for the large generated files. Do you notice much of a difference in the pausing/lockups if one of the large generated files is open? I have a feeling that keeping the 11k line document open while NCrunch is running may be the source of the problem.