NCrunch 1.32b exhausts Temp directory free space

Does NCrunch clean up its own temp directory usage? And if so, what criteria will trigger it?

I ask because I have set it to use a RAM disk for temp space but have needed to set the RAM disk larger than seems necessary and must periodically clean it by hand. When I do clean it I have to reset NCrunch or even the whole IDE to get NCrunch going again.

NCrunch takes responsibility for cleaning up after itself - so generally speaking you shouldn't need to do this yourself. If you try and remove the workspaces manually while the IDE is running, you'll definitely cause some very strange behaviour.

Internally NCrunch tracks the each individual workspace separately and will remove it as soon as is most efficient to do so. It's worth considering though that the way in which NCrunch pipelines its work can result in several near identical workspaces existing side-by-side, so it won't be sufficient to set your RAM drive as only just big enough for your solution (in practice you will need several times this amount).

You can reduce the disk space consumption by reducing the number of execution threads in your configuration. This will also reduce the engine's ability to run work in parallel though, so you'll notice a higher turnaround on your testing cycles.

Thanks for the detailed response, Remco.

I currently have the RAM disk set at 2x NCrunch's first-run consumed space but will try upping that to 3x or 4x and see how much better things go. Worst case I can point it back at the physical disk until I can requisition more RAM from IT (devs are only on 4GB around here, but I'm looking to change that.)

Cheers - would be good to hear how it goes for you :)