holes in cell node numbering result in 3.12 crashing without further notice
During legacy vtk unstructured grid import, if node numbers have holes like 0,1,2,4,5,... as common in finite element result files, version 3.12 crashes without giving any hint of what went wrong.
Please either do indicate that there is a problem with the node numbering or just fix the wrong numbering in paraview, by renumbering the nodes.
3 comments

AdminUtkarsh Ayachit (Admin, paraview) commented
Does this problem persist with 4.1? If so, can you provide a sample dataset?

finite element commented
POINTS are numbered consecutively, but if one exports the cells from a finite element model the node numbers sometimes might not be numbered consecutively.

finite element commented
that is node numbers in the CELLS definition