Hi, thanks for sharing this issue.

10GB is rather extreme, I haven't heard of the engine reaching so high before.

Can you give me any more statistics on on your solution in terms of code count, number of tests, and code coverage density?

Try deleting the NCrunch cache file to see if this resets the consumption. I'm curious as to whether it will return to 10GB after a full run through of your test suite.

The bulk of NCrunch's memory consumption is normally in its coverage index. Each individual line of covered code by every covered test must be recorded in this index. So if you have 1,000,000 lines of code, with each line covered by 10,000 tests, that will be 1,000,000 * 10,000 index entries. Are you able to construct any kind of rough estimate as to how many covered lines of code (by test) you have in your solution?

Interesting. It's definitely a leak then, not simply high memory consumption.

Let me know if you find a way to reproduce. It would be great if you could also keep an eye on your overall memory consumption across sessions to see if this increases over time. I'm wondering if somehow stale coverage data is accumulating across sessions.

Did you perhaps have a chance to see the size of the cache file before you deleted it?

Ok, that's good to know. Unfortunately, analysing this will be quite hard unless you're able to share your source code (which I don't usually expect). The cache file itself does actually contain quite a bit of your source code. It uses this to accurately preserve coverage data between sessions.

In your daily use of the product, do you very frequently do any of the following?

- Move projects around on disk
- Rename namespaces or tests
- Ignore/unignore large numbers of tests
- Add or remove large numbers of tests from the solution/projects
- Perform large scale refactoring on your codebase (esp renames on classes that are heavily covered)

An interesting test would be for you to unload and reload your test project a few times, and see if this makes a difference in the size of the cache file.

Do you often update from SVN with the NCrunch engine running? Or do you usually disable it when you update?

After some more observation it seems, that loading and unloading project has an impact on the growth rate of the memory consumption. I started to use the extension Funnel, where you can switch between different loaded solution configurations. This seem to speed up the allocation of memory faster, than it did before.

I think it is by unloading and reloading projects, only with funnel this happens a lot faster, as I unload / reload more often.

Hi, thanks for sharing this issue.

Svchost.exe is used to host a range of services and O/S level software. This won't be hosting any of NCrunch's code, but because NCrunch executes builds and test code, I would say there is a likelihood here that it is triggering this problem indirectly.

Do you have any integration tests running under NCrunch? Does disabling them make any difference? I suggest trying to deductively discover where the leak is coming from. You could try setting the engine to manual mode, then making a few changes to your solution to see if this brings up the problem. If the problem does not appear when the engine is in manual mode, you could try selectively disabling tests until you can find the one(s) responsible.

There must be a build step that is causing this. Are you able to narrow it down to a specific project? Do you have any projects in your solution that could be considered unusual?