I am trying to create a cinema database with an in-situ app using PV5.10.0-RC2 but it keeps crashing. Other extractor (such as data extractor or image extractor) work very well.
I have tried the same with the provided examples in Examples/Catalyst2/CxxFullExample and I see the same crash:
Stack trace:
12 0x564361857c5e ./bin/CxxFullExampleV2(+0xec5e) [0x564361857c5e]
11 0x7f9080d4b565 __libc_start_main + 213
10 0x564361857b7f ./bin/CxxFullExampleV2(+0xeb7f) [0x564361857b7f]
9 0x56436185dca1 ./bin/CxxFullExampleV2(+0x14ca1) [0x56436185dca1]
8 0x7f90789e893d /local/apps/ParaView/ParaView-v5.10Build/lib/catalyst/libcatalyst-paraview.so(+0xe93d) [0x7f90789e893d]
7 0x7f90789cf102 vtkInSituInitializationHelper::ExecutePipelines(int, double, std::vector<std::string> const&) + 242
6 0x7f9078788b0f vtkCPPythonScriptV2Helper::CatalystExecute(int, double, std::vector<std::string> const&) + 559
5 0x7f90784e41d4 vtkSMExtractsController::Extract(vtkCollection*) + 116
4 0x7f90784e3f87 vtkSMExtractsController::Extract(vtkSMProxy*) + 343
3 0x7f906528fe6f vtkSMImageExtractWriterProxy::Write(vtkSMExtractsController*) + 431
2 0x7f90652875ad vtkSMCinemaVolumetricImageExtractWriterProxy::WriteInternal(vtkSMExtractsController*, std::map<std::string, std::string, std::less<std::string>, std::allocator<std::pair<std::string const, std::string > > > const&) + 2317
1 0x7f907852e5d8 vtkSMPropertyHelper::vtkSMPropertyHelper(vtkSMProxy*, char const*, bool) + 40
0 0x7f9080d64040 /lib/x86_64-linux-gnu/libc.so.6(+0x41040) [0x7f9080d64040]
( 0.831s) [pvbatch ] :0 FATL| Signal: SIGSEGV
would this message ring a bell to any developer out there?