WIP: Expose bug in FlyingEdges
There appears to be some conditions where compute pass 4 of FlyingEdges does not properly update all of the values in InterpolationEdgeIds, which can cause failures when you later try to use these ids for edge interpolation.
The error is most noticible on debug builds of Windows, which initialize the bytes in allocated arrays with 0xCD. This is a negative number in 2's complement, which is an obviously invalid id. You should be able to replicate this behavior by editing FlyingEdges.h around line 170 to initialize sharedState.InterpolationEdgeIds to a bunch of negative numbers.
I think the problem is related to defining 2 or more isovalues. That seems to be when the error occurs. Maybe arrays are not getting windowed correctly.