Hi, thanks for sharing this issue.

This is likely being caused by NCrunch's instrumentation. There must be something in the CLR that doesn't like code within the exception filter from being instrumented. It's interesting that this only happens on Windows 10. I'll need to investigate this more before I can arrange a fix.

For the time being, I recommend disabling instrumentation on this code using NCrunch's code coverage suppression comments, for example:

try
{
// Do something
}
//ncrunch: no coverage start
catch ( AggregateException ex ) when ( ex.InnerException is HttpException ) { } // removing when-predicate gets rid of the InvalidProgramException
//ncrunch: no coverage end

Hi! Yes, I've managed to isolate and resolve this issue. A fix will be available with 2.27, out within the next couple of days.

It was actually a bug in Cecil, since fixed in Cecil's main dev branch. It wasn't correctly calculating the max stack size for methods using exception filters. Up until recently, the bug hadn't been a big deal because exception filters weren't available in C#. The issue didn't appear for all methods, because sometimes methods would have other code that would increase the max size of the stack over the required threshold. This made it hard to reproduce without a good code sample. Changing the structure of the method by adding extra method calls outside the exception filter will probably solve it in isolated situations.