ParaView crashes creating vtkMPIImageReader when reading raw data files on serial builds
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
There is a bug in ParView, local client, MPI turned off, where ParaView is trying to read raw data with the MPI based vtkMPIImageReader. This is a bug. Should replicate with any raw data, but I replicated it with volums_ex.out (knox).
I am replicating this bug on a local build of ParaView, Master or 3.98.1, PARAVIEW_USE_MPI set to off, Linux, local server.
Here is a thread between Utkarsh and me:
Yup, that;s bug. I am guessing in that happened somewhere during the movement of classes for modularization in one way or the other. Can you report a bug please? I'll have it fixed.
So, assuming that we shouldn't have a reader called vtkMPIImageReader in a non MPI build, why do I find the following in readers.xml? Is this setting up for remote server, or is it a bug? I don't find another ImageReader in this file.
On Fri, Mar 22, 2013 at 8:24 PM, Scott, W Alan firstname.lastname@example.org wrote:
I have a build of ParaView (both 3.98.1 and master) that is failing when trying to read raw data files. The Kitware binaries successfully read this raw data. The error message is as follows:
ERROR: In ..../src/ParaView3/ParaViewCore/ServerImplementation/Core/vtkSIProxy. c xx , line 307 vtkSISourceProxy (0x17bc94a0): Failed to create vtkMPIImageReader. Aborting for debugging purposes.
Anyone have any ideas?