egl-pvserver 5.11.0 MPI and OpenVDB

I am testing 5.11.0 Linux build I downloaded from the official site

Loading OpenVDB files locally with ParaView 5.11.0 display fine

Loading OpenVDB files remotely via a single instance of pvserver also display fine
e.g.

/data2/nyue/systems/ParaView/5.11.0/ParaView-5.11.0-egl-MPI-Linux-Python3.9-x86_64/bin/mpiexec -np 1 /data2/nyue/systems/ParaView/5.11.0/ParaView-5.11.0-egl-MPI-Linux-Python3.9-x86_64/bin/pvserver

However, if I were to invoke 2 processes via mpiexec, loading OpenVDB files will crash pvserver

/data2/nyue/systems/ParaView/5.11.0/ParaView-5.11.0-egl-MPI-Linux-Python3.9-x86_64/bin/mpiexec -np 2 /data2/nyue/systems/ParaView/5.11.0/ParaView-5.11.0-egl-MPI-Linux-Python3.9-x86_64/bin/pvserver

Is OpenVDB file/format not compatible for use in an MPI setting ?
Crash log

Waiting for client...
Connection URL: cs://head0:11111
Accepting connection(s): head0:11111
Client connected.

Loguru caught a signal: SIGSEGV

Loguru caught a signal: SIGSEGV
Stack trace:
25            0x40196d /data2/nyue/systems/ParaView/5.11.0/ParaView-5.11.0-egl-MPI-Linux-Python3.9-x86_64/bin/pvserver-real() [0x40196d]
24      0x7f95923b3c87 __libc_start_main + 231
23            0x4018c6 /data2/nyue/systems/ParaView/5.11.0/ParaView-5.11.0-egl-MPI-Linux-Python3.9-x86_64/bin/pvserver-real() [0x4018c6]
22      0x7f958ed12775 vtkMultiProcessController::ProcessRMIs(int, int) + 613
21      0x7f958ed11f93 vtkMultiProcessController::BroadcastProcessRMIs(int, int) + 211
20      0x7f958ed11c30 vtkMultiProcessController::ProcessRMI(int, void*, int, int) + 288
19      0x7f959063d472 vtkPVSessionCore::ExecuteStreamSatelliteCallback() + 162
18      0x7f959063d222 vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool) + 242
17      0x7f958f969b0d vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) + 29
16      0x7f958f96986e vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) + 1294
15      0x7f958f96913d vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) + 1229
14      0x7f958f968973 vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) + 355
13      0x7f9591088eab vtkSISourceProxyCommand(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*) + 971
12      0x7f959067a194 vtkSISourceProxy::UpdatePipeline(int, double, bool) + 468
11      0x7f958e849d7a vtkStreamingDemandDrivenPipeline::Update(int, vtkInformationVector*) + 282
10      0x7f958e7d863a vtkDemandDrivenPipeline::UpdateData(int) + 138
9       0x7f958e8484f9 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 953
8       0x7f958e7da01e vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 222
7       0x7f958e7d2651 vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*) + 337
6       0x7f958e8484f9 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 953
5       0x7f958e7da07a vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 314
4       0x7f958e7d3779 vtkCompositeDataPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 121
3       0x7f958e7d6c3d vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 29
2       0x7f958e84b9ac vtkStreamingDemandDrivenPipeline::ExecuteDataStart(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 332
1       0x7f958e7e4540 vtkExtentTranslator::PieceToExtentThreadSafe(int, int, int, int*, int*, int, int) + 16
0       0x7f95923d0f10 /lib/x86_64-linux-gnu/libc.so.6(+0x3ef10) [0x7f95923d0f10]
(  78.119s) [pvserver.1      ]                       :0     FATL| Signal: SIGSEGV
Stack trace:
27            0x40196d /data2/nyue/systems/ParaView/5.11.0/ParaView-5.11.0-egl-MPI-Linux-Python3.9-x86_64/bin/pvserver-real() [0x40196d]
26      0x7f291fcf9c87 __libc_start_main + 231
25            0x40184b /data2/nyue/systems/ParaView/5.11.0/ParaView-5.11.0-egl-MPI-Linux-Python3.9-x86_64/bin/pvserver-real() [0x40184b]
24      0x7f291d7acfe2 vtkTCPNetworkAccessManager::ProcessEventsInternal(unsigned long, bool) + 690
23      0x7f291c658765 vtkMultiProcessController::ProcessRMIs(int, int) + 597
22      0x7f291c657c30 vtkMultiProcessController::ProcessRMI(int, void*, int, int) + 288
21      0x7f291df8c940 vtkPVSessionServer::OnClientServerMessageRMI(void*, int) + 272
20      0x7f291df81d75 vtkPVSessionBase::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 53
19      0x7f291df8305b vtkPVSessionCore::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 59
18      0x7f291df83222 vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool) + 242
17      0x7f291d2afb0d vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) + 29
16      0x7f291d2af86e vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) + 1294
15      0x7f291d2af13d vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) + 1229
14      0x7f291d2ae973 vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) + 355
13      0x7f291e9ceeab vtkSISourceProxyCommand(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*) + 971
12      0x7f291dfc0194 vtkSISourceProxy::UpdatePipeline(int, double, bool) + 468
11      0x7f291c18fd7a vtkStreamingDemandDrivenPipeline::Update(int, vtkInformationVector*) + 282
10      0x7f291c11e63a vtkDemandDrivenPipeline::UpdateData(int) + 138
9       0x7f291c18e4f9 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 953
8       0x7f291c12001e vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 222
7       0x7f291c118651 vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*) + 337
6       0x7f291c18e4f9 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 953
5       0x7f291c12007a vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 314
4       0x7f291c119779 vtkCompositeDataPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 121
3       0x7f291c11cc3d vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 29
2       0x7f291c1919ac vtkStreamingDemandDrivenPipeline::ExecuteDataStart(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 332
1       0x7f291c12a540 vtkExtentTranslator::PieceToExtentThreadSafe(int, int, int, int*, int*, int, int) + 16
0       0x7f291fd16f10 /lib/x86_64-linux-gnu/libc.so.6(+0x3ef10) [0x7f291fd16f10]
(  78.119s) [pvserver.0      ]                       :0     FATL| Signal: SIGSEGV
error: exception occurred: Segmentation fault

===================================================================================
=   BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
=   PID 5993 RUNNING AT head0
=   EXIT CODE: 9
=   CLEANING UP REMAINING PROCESSES
=   YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
===================================================================================
YOUR APPLICATION TERMINATED WITH THE EXIT STRING: Killed (signal 9)
This typically refers to a problem with your application.
Please see the FAQ page for debugging suggestions

@Andy_Bauer @timothee.chabat

while the openvdb reader does not have a distributed version (maybe this will be improved later), it shouldn’t crash and just output all the data on rank 0 at least. I can reproduce on master so I opened an issue https://gitlab.kitware.com/paraview/paraview/-/issues/21665