Hi, thanks for posting.

We don't have anything built-in that can do this. Given that the tests themselves are your own code, perhaps it might be possible for you to engineer something into the tests themselves? For example, you could create a SetUpFixture that starts a background thread which monitors the amount of memory in use in the process. When the memory usage hits a threshold, it enumerates all threads in the process and captures the stack trace of each one, then writes this to a file on disk.

Something else you could try is to declare the NCrunch.Framework.IsolatedAttribute at assembly level in your test projects. NCrunch will then run each fixture in its own process. This might help reduce the data you need to sift through if you can identify a specific process that's eating more than it should.