Segmentation fault when loading Tecplot binary files


I’m unable to load Tecplot binary files with Paraview (via the Visit module). Everytime I hit “apply” Paraview crashes. I can load these files with tecplot, and I can load Tecplot ascii files with Paraview, so I think it’s a problem with the Visit module. Due to the large size of the solution files I’s rather use the binary version instead of the ascii version. Is there maybe some workaround or fix for this problem?

Some infomation about my setup:
OS: OpenSuse 42.2 64bit
Paraview version I tried: 5.5.2 and 5.60-RC2 (pre-compiled from the downloads page) and the latest build from github, self compiled

Unfortunately, paraview didn’t give me any information about the error, so I do’t know what else I could tell you…

Could you run it in a debugger and get a stack trace where the crash occurs? That would be helpful. In addition, if you have a small example Tecplot binary file that makes ParaView crash that you can occur, that would also be helpful for debugging. Thanks.

Sorry for the late reply, I first had to create a suitable mesh to share. However, unfortunately it is still too big (10MB), so I can’t upload it. Can I send it to you via email?

And here is the output gdb is giving me:

(gdb) run
Starting program: /home/****/Programme/paraview-debug/bin/paraview 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/".
[New Thread 0x7fffcd78c700 (LWP 24368)]
[New Thread 0x7fffc7fff700 (LWP 24372)]

Thread 1 "paraview" received signal SIGSEGV, Segmentation fault.
0x00007fffd2d506b2 in vtkUnstructuredGridRelevantPointsFilter::RequestData (this=0x39fcb30, inputVector=0x3a9e2b0, 
    at /home/****/Programme/paraview/Utilities/VisItBridge/Library/VisItLib/visit_vtk/full/vtkUnstructuredGridRelevantPointsFilter.C:127
127           if (pointMap[oldPt] == -1)

Thank you for your help!

edit: I managed to reduce the size a bit, you can find the example attached to this post.
Cylinder_Surface.plt (2.0 MB)

Thanks for the dataset. I’ll take a look.

I was able to reproduce the crash, but I do not have a fix for it unfortunately.

I suggest filing a bug report at so we do not loose track of this bug. I can’t give an estimate for when it will be fixed, though.

1 Like