Hi Wojtek,

Thanks for posting!

Yes - stack overflows are tough to deal with. I have a plan that should allow NCrunch to tackle this tidily, though it will take a bit of work and fortunately these issues are relatively rare in a developer's workday (unless your writing some manically recursive code). You'll notice that when these happen, the engine should just throw up and error and then carry on as usual.


Cheers,

Remco

You're right in that dealing with stack overflows isn't simple. A stack overflow will rip through any exception trap and will religiously take down the process executing the offending code. The key issue is that when the process runs out of stack, it often works its way into an invalid state. The CLR does have some reliability features to allow proper cleanup after a stack overflow as occurred, but these are limited to damage control and reviving the process is extremely difficult to do. I do have some plans on handling them more gracefully in NCrunch - through it will likely involve letting the process die a natural death and simply trying to improve the user experience and pipeline management around this. Stay tuned :)