filedriver.py inconsistently seg faulting
@utkarsh.ayachit @cory.quammen
Using the filedriver.py from the current master branch to test catalyst scripts is inconsistently seg faulting. I am running MacOS 10.14.6 with pvbatch from the 5.8.0 binary. The catalyst script used is gridwriter.py from the ParaView source.
Using a bash script:
#!/bin/bash
rm -rf input_0*
rm *pyc
/Applications/ParaView-5.8.0.app/Contents/bin/pvbatch \
-sym -dr /Users/stam/projects/paraview/src/Examples/Catalyst/SampleScripts/filedriver.py \
/Users/stam/projects/data-paraview/vtm_can_ex2/can_ex2_0.vtm \
/Users/stam/projects/paraview/src/test_filedriver/gridwriter.py
when running that bash script repeatedly (~6 to 10 times in a row), sometimes it works, sometimes I get the error:
Reading in ['/Users/stam/projects/data-paraview/vtm_can_ex2/can_ex2_0.vtm']
Adding script /Users/stam/projects/paraview/src/Examples/Catalyst/SampleScripts/gridwriter.py
The channel name is input
Loguru caught a signal: SIGSEGV
Stack trace:
8 0x6 12 ??? 0x0000000000000006 0x0 + 6
7 0x7fff5ebda3dc start + 8
6 0x7fff5ec806b3 exit + 55
5 0x7fff5ec803cf __cxa_finalize_ranges + 319
4 0x7fff5be0ed42 std::__shared_weak_count::__release_shared() + 40
3 0x122b3fa75 ospray::api::ISPCDevice::~ISPCDevice() + 37
2 0x122f6ab91 rtcReleaseDevice + 385
1 0x122f53c35 embree::Device::process_error(embree::Device*, RTCError, char const*) + 453
0 0x0 4 ??? 0x0000000000000000 0x0 + 0
( 1.618s) [pvbatch ] :0 FATL| Signal: SIGSEGV
./test_filedriver.sh: line 13: 74978 Segmentation fault: 11 /Applications/ParaView-5.8.0.app/Contents/bin/pvbatch -sym -dr /Users/stam/projects/paraview/src/Examples/Catalyst/SampleScripts/filedriver.py /Users/stam/projects/data-paraview/vtm_can_ex2/can_ex2_0.vtm /Users/stam/projects/paraview/src/Examples/Catalyst/SampleScripts/gridwriter.py
Are you able to reproduce? Do you have guidance for what to do/what not to do?