Hi Sam -

Thanks for sharing this issue. Unfortunately, because of the number of components and variables involved, this may be a tough one to isolate. I'm wondering if you might be able to help by answering the following questions:

- Does this happen only when you debug using NCrunch? Or when you debug in general?
- Does this happen for a specific solution, or for all solutions on your machine?
- Do you have any colleagues or team members with a similar environment working on your project with NCrunch? If so, do they also experience this problem?
- Can you share some more details about the setup of your system? I.e. which O/S, CPU, amount of memory?
- Do you have any other VS plugins installed?


Thanks!

Remco

Hi Sam,

NCrunch itself doesn't tinker with the debugger outside of its own debug actions (i.e. when you instruct it to debug or break into a test), so as you've mentioned that this only started after NCrunch was installed, this leads me to suspect one of the following:

- The installation of NCrunch has triggered an unrelated configuration change or corruption issue within Visual Studio itself that causes the behaviour to appear randomly. VS plugins are usually installed with the "devenv.exe /setup" option, which causes a cascade of changes and refreshing of VS data that can sometimes surface problems if the setup operation didn't work correctly. Try executing "devenv.exe /setup", waiting for the process to complete, then restart your computer and see if this makes any difference.
- The usage of NCrunch has resulted in increased memory utilisation on your machine, thereby providing the tipping point beyond which the machine becomes unstable
- There is something else going on here with an unrelated piece of software that we haven't yet identified

I think it would be worth doing some experimentation to try and narrow down the issue. Does working without NCrunch installed make the issue go away? Or can you find a clear pattern around memory utilisation when the issue appears?


Cheers,

Remco