Segmentation fault. Loguru caught a signal: SIGSEGV

Segfaults? I have not seen something like that. Would you mind reporting such issue?

Don’t have the dataset in hand. But definitely recall such errors when developing a filter.

Will report when I see one!

1 Like

Segfaults usually originate from out of memory accesses so, if you feed garbage to an algorithm that does not expect garbage then you are probably gonna have a problem. We could have an output consistency test at least memory access wise, but that’s gonna be an overhead for sure.

Yep, in the reported stack trace, the access violation originates from vtkGeometryRepresentationWithFaces. Those sanity checks you suggested would definitely help in both situations (readers and filters)