Contour filter causes segmentation fault during insitu operation.
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
Placing a contour filter in an in-situ python file appears to cause a segmentation fault, at least when done in the manner of the python file generated by the insitu coprocessing plug in.
To replicate error do the following:
Load a dataset, presumably an exodus file.
Apply a contour filter with a single contour value at a reasonable setting (e.g. at halfway between the min and the max of a given scalar point value).
Export an insitu python file using the coprocessing plugin.
Try to run insitu using the produced python file. A segmentation violation results. In particular, it occurs when the python file tries to execute the Show() function after setting the active source to the given contour operation. For example in my python file we have:
SetActiveSource(Contour1) DataRepresentation2 = Show()
And the segmentation violation occurs when Show() is executed. SetActiveSource() does not cause a segmentation violation, and the creation of the Contour1 filter earlier in the operation does not cause a segmentation violation.