This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
VTK segfaults on GNU/Linux+Python when it reads in a VRML IndexedFaceSet which contains no 'coordIndex' component, i.e. only points. The file can be "corrected" and loaded with no segfault by adding an empty coordIndex [ ] entry to the IndexedFaceSet node. I checked out the spec. for VRML 2.0, but it's unclear if coordIndex's are required or, if not, what the default behavior should be. In either case I would expect VTK to handle the error gracefully.
Here's the VRML2 spec. I was looking at: http://provar.stanford.edu/papers/vrml2spec/spec/part1/nodesRef.html#IndexedFaceSet