ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2021-03-24T09:36:55-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/20537pv.LagrangianSurfaceHelperNone: produces arrays with mismatched type2021-03-24T09:36:55-04:00Utkarsh Ayachitpv.LagrangianSurfaceHelperNone: produces arrays with mismatched typeRun `pv.LagrangianSurfaceHelperNone` and you'll get an error message
```
( 692.968s) [paraview ] vtkDataArray.cxx:522 ERR| vtkIntArray (0x557a3aa5ba60): Type mismatch: Source: double Dest: int
```
This is happening beca...Run `pv.LagrangianSurfaceHelperNone` and you'll get an error message
```
( 692.968s) [paraview ] vtkDataArray.cxx:522 ERR| vtkIntArray (0x557a3aa5ba60): Type mismatch: Source: double Dest: int
```
This is happening because the 'SurfaceType' array has different type on different blocks. Is this necessary? Creating such arrays with different types for same name can confuse many things -- in this case, it's the `vtkSortedTableStreamer` used the spreadsheet view that throws this error message.Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/20533VTK_USE_X + VTK_HAS_EGL segfault and warns2021-03-24T09:37:25-04:00Mathieu Westphal (Kitware)VTK_USE_X + VTK_HAS_EGL segfault and warnsThe following build configuration fails to provide expected behavior
```
VTK_USE_X = ON
VTK_HAS_EGL = ON
PARAVIEW_USE_PYTHON = ON
```
* Build successful
* ParaView Run and render successfully with a lot of warnings (probably related t...The following build configuration fails to provide expected behavior
```
VTK_USE_X = ON
VTK_HAS_EGL = ON
PARAVIEW_USE_PYTHON = ON
```
* Build successful
* ParaView Run and render successfully with a lot of warnings (probably related to #20531 )
`GLEW could not be initialized: Missing GL version`
* pvpython onscreen : **segfault with errors in log**: `GLEW could not be initialized: Missing GL version`
* pvpython offscreen successful
This behavior is not expected. EGL + X should support onscreen render correctly, either from ParaView or pvpython.
FYI @utkarsh.ayachit @ben.boeckel @timothee.chabathttps://gitlab.kitware.com/paraview/paraview/-/issues/20532PARAVIEW_ENABLE_QT + VTK_HAS_OSMESA segfault2021-03-24T09:38:40-04:00Mathieu Westphal (Kitware)PARAVIEW_ENABLE_QT + VTK_HAS_OSMESA segfaultThe following build configuration fails to provide expected behavior
```
VTK_USE_X=OFF
VTK_HAS_OSMESA=ON
PARAVIEW_ENABLE_QT=ON
```
- configure: OK
- build: OK
- ParaView run: Segfault
```
warning: In unknown, line 0
warning: Unrecogni...The following build configuration fails to provide expected behavior
```
VTK_USE_X=OFF
VTK_HAS_OSMESA=ON
PARAVIEW_ENABLE_QT=ON
```
- configure: OK
- build: OK
- ParaView run: Segfault
```
warning: In unknown, line 0
warning: Unrecognized OpenGL version
[...]
( 0.561s) [paraview ]vtkOpenGLRenderWindow.c:477 ERR| vtkGenericOpenGLRenderWindow (0x560f97ff4eb0): GLEW could not be initialized: Missing GL version
Loguru caught a signal: SIGSEGV
```
FYI @ben.boeckel @utkarsh.ayachit @timothee.chabathttps://gitlab.kitware.com/paraview/paraview/-/issues/20531PARAVIEW_ENABLE_QT + VTK_HAS_EGL warns on each render2021-03-24T09:38:47-04:00Mathieu Westphal (Kitware)PARAVIEW_ENABLE_QT + VTK_HAS_EGL warns on each renderThe following build configuration fails to provide expected behavior
```
PARAVIEW_ENABLE_QT = ON
VTK_HAS_EGL = ON
VTK_USE_X = OFF
```
* Build successful
* ParaView Run and render successfully with warning at each render
`GLEW could no...The following build configuration fails to provide expected behavior
```
PARAVIEW_ENABLE_QT = ON
VTK_HAS_EGL = ON
VTK_USE_X = OFF
```
* Build successful
* ParaView Run and render successfully with warning at each render
`GLEW could not be initialized: Missing GL version`
This behavior is not expected, there shouldn't be any warnings.
FYI @ben.boeckel @timothee.chabat @utkarsh.ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20514Crash with redistribute dataset on slice2021-08-11T11:45:13-04:00Nicolas VuailleCrash with redistribute dataset on sliceTested with PV 5.9.0 and master
* `mpirun -n 2 ./bin/pvserver`
* `./bin/paraview`
* Connect
* Wavelet
* Slice
* Redistribute Dataset
-> crash
gdb trace
----
```llvm
#0 0x00007ffff7e14ef5 in raise () from /usr/lib/libc.so.6
#1 ...Tested with PV 5.9.0 and master
* `mpirun -n 2 ./bin/pvserver`
* `./bin/paraview`
* Connect
* Wavelet
* Slice
* Redistribute Dataset
-> crash
gdb trace
----
```llvm
#0 0x00007ffff7e14ef5 in raise () from /usr/lib/libc.so.6
#1 0x00007ffff7dfe862 in abort () from /usr/lib/libc.so.6
#2 0x00007ffff3c4486a in __gnu_cxx::__verbose_terminate_handler () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/vterminate.cc:95
#3 0x00007ffff3c50d3a in __cxxabiv1::__terminate (handler=<optimized out>) at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:48
#4 0x00007ffff3c50da7 in std::terminate () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:58
#5 0x00007ffff3c5104e in __cxxabiv1::__cxa_throw (obj=<optimized out>, tinfo=0x7ffff3d7d280 <typeinfo for std::runtime_error>, dest=0x7ffff3c66f80 <std::runtime_error::~runtime_error()>)
at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_throw.cc:95
#6 0x00007fffefd0ff15 in vtkdiy2::detail::KDTreePartition<(anonymous namespace)::BlockT, (anonymous namespace)::PointTT>::compute_local_histogram (this=0x55555783a220, b=0x5555577baf10, srp=..., dim=0)
at ../VTK/ThirdParty/diy2/vtkdiy2/include/vtkdiy2/detail/algorithms/kdtree.hpp:381
#7 0x00007fffefd0dc6d in vtkdiy2::detail::KDTreePartition<(anonymous namespace)::BlockT, (anonymous namespace)::PointTT>::operator() (this=0x55555783a220, b=0x5555577baf10, srp=..., partners=...)
at ../VTK/ThirdParty/diy2/vtkdiy2/include/vtkdiy2/detail/algorithms/kdtree.hpp:201
#8 0x00007fffefd0b87a in std::__invoke_impl<void, vtkdiy2::detail::KDTreePartition<(anonymous namespace)::BlockT, (anonymous namespace)::PointTT>&, (anonymous namespace)::BlockT*, vtkdiy2::ReduceProxy const&, vtkdiy2::detail::KDTreePartners const&> (__f=...) at /usr/include/c++/10.2.0/bits/invoke.h:60
#9 0x00007fffefd0b032 in std::__invoke_r<void, vtkdiy2::detail::KDTreePartition<(anonymous namespace)::BlockT, (anonymous namespace)::PointTT>&, (anonymous namespace)::BlockT*, vtkdiy2::ReduceProxy const&, vtkdiy2::detail::KDTreePartners const&> (__fn=...) at /usr/include/c++/10.2.0/bits/invoke.h:153
#10 0x00007fffefd0a548 in std::_Function_handler<void((anonymous namespace)::BlockT*, const vtkdiy2::ReduceProxy&, const vtkdiy2::detail::KDTreePartners&), vtkdiy2::detail::KDTreePartition<(anonymous namespace)::BlockT, (anonymous namespace)::PointTT> >::_M_invoke(const std::_Any_data &, (anonymous namespace)::BlockT *&&, const vtkdiy2::ReduceProxy &, const vtkdiy2::detail::KDTreePartners &) (__functor=...,
__args#0=@0x7fffffffaae0: 0x5555577baf10, __args#1=..., __args#2=...) at /usr/include/c++/10.2.0/bits/std_function.h:291
#11 0x00007fffefd11042 in std::function<void((anonymous namespace)::BlockT*, const vtkdiy2::ReduceProxy&, const vtkdiy2::detail::KDTreePartners&)>::operator()((anonymous namespace)::BlockT *, const vtkdiy2::ReduceProxy &, const vtkdiy2::detail::KDTreePartners &) const (this=0x555557839fa8, __args#0=0x5555577baf10, __args#1=..., __args#2=...) at /usr/include/c++/10.2.0/bits/std_function.h:622
#12 0x00007fffefd10451 in vtkdiy2::detail::ReductionFunctor<(anonymous namespace)::BlockT, vtkdiy2::detail::KDTreePartners>::operator() (this=0x555557839fa0, b=0x5555577baf10, cp=...)
at ../VTK/ThirdParty/diy2/vtkdiy2/include/vtkdiy2/reduce.hpp:187
#13 0x00007fffefd0df2a in std::__invoke_impl<void, vtkdiy2::detail::ReductionFunctor<(anonymous namespace)::BlockT, vtkdiy2::detail::KDTreePartners>&, (anonymous namespace)::BlockT*, vtkdiy2::Master::ProxyWithLink const&> (__f=...) at /usr/include/c++/10.2.0/bits/invoke.h:60
#14 0x00007fffefd0ba77 in std::__invoke_r<void, vtkdiy2::detail::ReductionFunctor<(anonymous namespace)::BlockT, vtkdiy2::detail::KDTreePartners>&, (anonymous namespace)::BlockT*, vtkdiy2::Master::ProxyWithLink const&> (__fn=...) at /usr/include/c++/10.2.0/bits/invoke.h:153
#15 0x00007fffefd0b1ae in std::_Function_handler<void((anonymous namespace)::BlockT*, const vtkdiy2::Master::ProxyWithLink&), vtkdiy2::detail::ReductionFunctor<(anonymous namespace)::BlockT, vtkdiy2::detail::KDTreePartners> >::_M_invoke(const std::_Any_data &, (anonymous namespace)::BlockT *&&, const vtkdiy2::Master::ProxyWithLink &) (__functor=..., __args#0=@0x7fffffffad20: 0x5555577baf10, __args#1=...)
at /usr/include/c++/10.2.0/bits/std_function.h:291
#16 0x00007fffefd1231d in std::function<void((anonymous namespace)::BlockT*, const vtkdiy2::Master::ProxyWithLink&)>::operator()((anonymous namespace)::BlockT *, const vtkdiy2::Master::ProxyWithLink &) const (
this=0x55555783e978, __args#0=0x5555577baf10, __args#1=...) at /usr/include/c++/10.2.0/bits/std_function.h:622
#17 0x00007fffefd12215 in vtkdiy2::Master::Command<(anonymous namespace)::BlockT>::execute (this=0x55555783e970, b=0x5555577baf10, cp=...)
at ../VTK/ThirdParty/diy2/vtkdiy2/include/vtkdiy2/detail/master/commands.hpp:16
#18 0x00007fffefd18a3f in vtkdiy2::Master::ProcessBlock::operator() (this=0x7fffffffaed0) at ../VTK/ThirdParty/diy2/vtkdiy2/include/vtkdiy2/detail/master/execution.hpp:61
#19 0x00007fffefd190ba in vtkdiy2::Master::execute (this=0x7fffffffbb50) at ../VTK/ThirdParty/diy2/vtkdiy2/include/vtkdiy2/detail/master/execution.hpp:149
#20 0x00007fffefd0a839 in vtkdiy2::Master::foreach_<(anonymous namespace)::BlockT> (this=0x7fffffffbb50, f=..., skip=...) at ../VTK/ThirdParty/diy2/vtkdiy2/include/vtkdiy2/master.hpp:631
#21 0x00007fffefd09fb2 in vtkdiy2::Master::foreach<vtkdiy2::detail::ReductionFunctor<(anonymous namespace)::BlockT, vtkdiy2::detail::KDTreePartners> > (this=0x7fffffffbb50, f=..., s=...)
at ../VTK/ThirdParty/diy2/vtkdiy2/include/vtkdiy2/master.hpp:261
#22 0x00007fffefd0952a in vtkdiy2::reduce<vtkdiy2::detail::KDTreePartition<(anonymous namespace)::BlockT, (anonymous namespace)::PointTT>, vtkdiy2::detail::KDTreePartners, vtkdiy2::detail::ReduceNeverSkip> (
master=..., assigner=..., partners=..., reduce=..., skip=...) at ../VTK/ThirdParty/diy2/vtkdiy2/include/vtkdiy2/reduce.hpp:125
#23 0x00007fffefd0827d in vtkdiy2::reduce<vtkdiy2::detail::KDTreePartition<(anonymous namespace)::BlockT, (anonymous namespace)::PointTT>, vtkdiy2::detail::KDTreePartners> (master=..., assigner=...,
partners=..., reducer=...) at ../VTK/ThirdParty/diy2/vtkdiy2/include/vtkdiy2/reduce.hpp:163
#24 0x00007fffefd071d7 in vtkdiy2::kdtree<(anonymous namespace)::BlockT, (anonymous namespace)::PointTT> (master=..., assigner=..., dim=3, domain=..., points=&(anonymous namespace)::BlockT::Points, bins=256,
wrap=false) at ../VTK/ThirdParty/diy2/vtkdiy2/include/vtkdiy2/algorithms.hpp:121
#25 0x00007fffefd04cf4 in vtkDIYKdTreeUtilities::GenerateCuts (points=std::vector of length 1, capacity 1 = {...}, number_of_partitions=2, controller=0x55555571b830, local_bounds=0x7fffffffbef0)
at ../VTK/Filters/ParallelDIY2/vtkDIYKdTreeUtilities.cxx:239
#26 0x00007fffefd04003 in vtkDIYKdTreeUtilities::GenerateCuts (dobj=0x55555782ea40, number_of_partitions=2, use_cell_centers=true, controller=0x55555571b830, local_bounds=0x7fffffffbff0)
at ../VTK/Filters/ParallelDIY2/vtkDIYKdTreeUtilities.cxx:122
#27 0x00007fffefe59d0b in vtkRedistributeDataSetFilter::GenerateCuts (this=0x555557531d70, dobj=0x55555782ea40) at ../VTK/Filters/ParallelDIY2/vtkRedistributeDataSetFilter.cxx:517
#28 0x00007fffefe59ade in vtkRedistributeDataSetFilter::InitializeCuts (this=0x555557531d70, input=0x55555782ea40) at ../VTK/Filters/ParallelDIY2/vtkRedistributeDataSetFilter.cxx:499
#29 0x00007fffefe590b9 in vtkRedistributeDataSetFilter::RequestData (this=0x555557531d70, inputVector=0x5555576a0f20, outputVector=0x555557835160)
at ../VTK/Filters/ParallelDIY2/vtkRedistributeDataSetFilter.cxx:387
#30 0x00007ffff54cce2e in vtkDataObjectAlgorithm::ProcessRequest (this=0x555557531d70, request=0x555557823990, inputVector=0x5555576a0f20, outputVector=0x555557835160)
at ../VTK/Common/ExecutionModel/vtkDataObjectAlgorithm.cxx:85
#31 0x00007ffff54d7497 in vtkExecutive::CallAlgorithm (this=0x555557832610, request=0x555557823990, direction=1, inInfo=0x5555576a0f20, outInfo=0x555557835160) at ../VTK/Common/ExecutionModel/vtkExecutive.cxx:746
#32 0x00007ffff54cf3fe in vtkDemandDrivenPipeline::ExecuteData (this=0x555557832610, request=0x555557823990, inInfo=0x5555576a0f20, outInfo=0x555557835160)
at ../VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx:462
#33 0x00007ffff54c3e74 in vtkCompositeDataPipeline::ExecuteData (this=0x555557832610, request=0x555557823990, inInfoVec=0x5555576a0f20, outInfoVec=0x555557835160)
at ../VTK/Common/ExecutionModel/vtkCompositeDataPipeline.cxx:162
#34 0x00007ffff54ceae6 in vtkDemandDrivenPipeline::ProcessRequest (this=0x555557832610, request=0x555557823990, inInfoVec=0x5555576a0f20, outInfoVec=0x555557835160)
at ../VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx:261
#35 0x00007ffff555515c in vtkStreamingDemandDrivenPipeline::ProcessRequest (this=0x555557832610, request=0x555557823990, inInfoVec=0x5555576a0f20, outInfoVec=0x555557835160)
at ../VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx:343
#36 0x00007ffff54c6707 in vtkCompositeDataPipeline::ForwardUpstream (this=0x555557506160, request=0x555557823990) at ../VTK/Common/ExecutionModel/vtkCompositeDataPipeline.cxx:727
#37 0x00007ffff54ce9e2 in vtkDemandDrivenPipeline::ProcessRequest (this=0x555557506160, request=0x555557823990, inInfoVec=0x555557856ad0, outInfoVec=0x5555577c7630)
at ../VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx:247
#38 0x00007ffff555515c in vtkStreamingDemandDrivenPipeline::ProcessRequest (this=0x555557506160, request=0x555557823990, inInfoVec=0x555557856ad0, outInfoVec=0x5555577c7630)
at ../VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx:343
#39 0x00007ffff54cf22d in vtkDemandDrivenPipeline::UpdateData (this=0x555557506160, outputPort=0) at ../VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx:419
#40 0x00007ffff55554f8 in vtkStreamingDemandDrivenPipeline::Update (this=0x555557506160, port=0, requests=0x0) at ../VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx:417
#41 0x00007ffff5555381 in vtkStreamingDemandDrivenPipeline::Update (this=0x555557506160, port=0) at ../VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx:380
#42 0x00007ffff637635f in vtkSISourceProxy::UpdatePipeline (this=0x555557849080, port=0, time=0, doTime=true) at ../Remoting/ServerManager/vtkSISourceProxy.cxx:255
#43 0x00007ffff6a870da in vtkSISourceProxyCommand (arlu=0x555555765c10, ob=0x555557849080, method=0x5555576a0ae9 "UpdatePipeline", msg=..., resultStream=...)
at CMakeFiles/vtkRemotingServerManagerCS/vtkSISourceProxyClientServer.cxx:139
#44 0x00007ffff5900c23 in vtkClientServerInterpreter::CallCommandFunction (this=0x555555765c10, cname=0x7ffff6517e94 "vtkSISourceProxy", ptr=0x555557849080, method=0x5555576a0ae9 "UpdatePipeline", msg=...,
result=...) at ../Remoting/ClientServerStream/vtkClientServerInterpreter.cxx:810
#45 0x00007ffff58ff244 in vtkClientServerInterpreter::ProcessCommandInvoke (this=0x555555765c10, css=..., midx=0) at ../Remoting/ClientServerStream/vtkClientServerInterpreter.cxx:424
#46 0x00007ffff58fe754 in vtkClientServerInterpreter::ProcessOneMessage (this=0x555555765c10, css=..., message=0) at ../Remoting/ClientServerStream/vtkClientServerInterpreter.cxx:265
#47 0x00007ffff58fe5db in vtkClientServerInterpreter::ProcessStream (this=0x555555765c10, css=...) at ../Remoting/ClientServerStream/vtkClientServerInterpreter.cxx:235
#48 0x00007ffff6325424 in vtkPVSessionCore::ExecuteStreamInternal (this=0x5555557672d0, stream=..., ignore_errors=false) at ../Remoting/ServerManager/vtkPVSessionCore.cxx:637
#49 0x00007ffff63252ef in vtkPVSessionCore::ExecuteStreamSatelliteCallback (this=0x5555557672d0) at ../Remoting/ServerManager/vtkPVSessionCore.cxx:620
#50 0x00007ffff6322e7c in (anonymous namespace)::RMICallback (localArg=0x5555557672d0, remoteArg=0x55555781baf0) at ../Remoting/ServerManager/vtkPVSessionCore.cxx:70
#51 0x00007ffff560a1e4 in vtkMultiProcessController::ProcessRMI (this=0x55555571b830, remoteProcessId=0, arg=0x55555781baf0, argLength=1, rmiTag=887822) at ../VTK/Parallel/Core/vtkMultiProcessController.cxx:741
#52 0x00007ffff560932e in vtkMultiProcessController::BroadcastProcessRMIs (this=0x55555571b830, dont_loop=0) at ../VTK/Parallel/Core/vtkMultiProcessController.cxx:530
#53 0x00007ffff56097c8 in vtkMultiProcessController::ProcessRMIs (this=0x55555571b830, reportErrors=1, dont_loop=0) at ../VTK/Parallel/Core/vtkMultiProcessController.cxx:628
#54 0x00007ffff560976c in vtkMultiProcessController::ProcessRMIs (this=0x55555571b830) at ../VTK/Parallel/Core/vtkMultiProcessController.cxx:620
#55 0x0000555555556644 in RealMain (argc=1, argv=0x7fffffffd6e8, type=vtkProcessModule::PROCESS_SERVER) at ../Clients/CommandLineExecutables/pvserver_common.h:94
#56 0x0000555555556702 in main (argc=1, argv=0x7fffffffd6e8) at ../Clients/CommandLineExecutables/pvserver.cxx:21
```https://gitlab.kitware.com/paraview/paraview/-/issues/20511Same texture in two different views not working correctly2022-05-02T03:40:18-04:00Timothee ChabatSame texture in two different views not working correctlyApplying the same texture in two different views does not work. It is kind of expected because it is not supported by VTK (see discussion on https://gitlab.kitware.com/vtk/vtk/-/issues/18336)
Steps to reproduce :
- Create a plane. App...Applying the same texture in two different views does not work. It is kind of expected because it is not supported by VTK (see discussion on https://gitlab.kitware.com/vtk/vtk/-/issues/18336)
Steps to reproduce :
- Create a plane. Apply.
- In the `Display` section, select and load a texture.
- Open a new layout (or split the current layout) and select Render View.
- Display the previously created plane.
- Apply the previously loaded texture to the plane in this view.
- Select the first view again : the texture will (or not, depending of your hardware) display wrongly the texture.
Visible warnings :
```
( 38.292s) [paraview ] vtkOpenGLState.cxx:166 WARN| Error in cache state for GL_ACTIVE_TEXTURE
( 38.298s) [paraview ] vtkOpenGLState.cxx:274 WARN| at stack loc
0x7f27877e2888 : ??? [(???) ???:-1]
0x7f27877dd355 : vtksys::SystemInformation::GetProgramStack[abi:cxx11](int, int) [(libvtksys-pv5.9.so.1) ???:-1]
0x7f278b642826 : vtkOpenGLState::CheckState() [(libvtkRenderingOpenGL2-pv5.9.so.1) ???:-1]
0x7f278b6468cc : vtkOpenGLState::SetEnumState(unsigned int, bool) [(libvtkRenderingOpenGL2-pv5.9.so.1) ???:-1]
0x7f278b647db1 : vtkOpenGLState::vtkglDisable(unsigned int) [(libvtkRenderingOpenGL2-pv5.9.so.1) ???:-1]
0x7f278b5f7b6d : vtkOpenGLProperty::Render(vtkActor*, vtkRenderer*) [(libvtkRenderingOpenGL2-pv5.9.so.1) ???:-1]
0x7f278516be09 : vtkPVLODActor::Render(vtkRenderer*, vtkMapper*) [(libvtkRemotingViews-pv5.9.so.1) ???:-1]
0x7f278ab23f95 : vtkActor::RenderTranslucentPolygonalGeometry(vtkViewport*) [(libvtkRenderingCore-pv5.9.so.1) ???:-1]
0x7f278ac4ccca : vtkProp::RenderFilteredTranslucentPolygonalGeometry(vtkViewport*, vtkInformation*) [(libvtkRenderingCore-pv5.9.so.1) ???:-1]
0x7f278b512a6b : vtkDefaultPass::RenderFilteredTranslucentPolygonalGeometry(vtkRenderState const*) [(libvtkRenderingOpenGL2-pv5.9.so.1) ???:-1]
0x7f278b6f7d0a : vtkTranslucentPass::Render(vtkRenderState const*) [(libvtkRenderingOpenGL2-pv5.9.so.1) ???:-1]
0x7f278b51c425 : vtkDualDepthPeelingPass::RenderTranslucentPass() [(libvtkRenderingOpenGL2-pv5.9.so.1) ???:-1]
0x7f278b51f7c6 : vtkDualDepthPeelingPass::PeelTranslucentGeometry() [(libvtkRenderingOpenGL2-pv5.9.so.1) ???:-1]
0x7f278b51e5da : vtkDualDepthPeelingPass::Peel() [(libvtkRenderingOpenGL2-pv5.9.so.1) ???:-1]
0x7f278b51a0fe : vtkDualDepthPeelingPass::Render(vtkRenderState const*) [(libvtkRenderingOpenGL2-pv5.9.so.1) ???:-1]
[...]
```
These warnings are not displayed when using the binary release of 5.9.1 but are when using my custom build.
Issue is reproducible if two separate planes are used. Also if we load a different texture for each view then we also have a correct behavior.https://gitlab.kitware.com/paraview/paraview/-/issues/20496ParaView 5.9.0 on MacOS Catalina saves broken screenshot and animation2021-04-07T11:06:06-04:00AlexeyParaView 5.9.0 on MacOS Catalina saves broken screenshot and animationParaView 5.9.0 on MacOS Catalina (10.15.7) on screenshots and animations adds white border around title text and decreases font sizes.
See the original ParaView window view:
![Screenshot_2021-02-22_at_01.11.19](/uploads/68f81eb038cf6557...ParaView 5.9.0 on MacOS Catalina (10.15.7) on screenshots and animations adds white border around title text and decreases font sizes.
See the original ParaView window view:
![Screenshot_2021-02-22_at_01.11.19](/uploads/68f81eb038cf65578c1b9d9537f3277a/Screenshot_2021-02-22_at_01.11.19.jpg)
And the same view saved on ParaView screenshot:
![screenshot](/uploads/18e9a7e6d163d913a239a2d471b75b68/screenshot.jpg)https://gitlab.kitware.com/paraview/paraview/-/issues/20494Slice filter produce duplicated points with unstructured grid input2021-03-24T09:23:06-04:00Mathieu Westphal (Kitware)Slice filter produce duplicated points with unstructured grid inputSlice filter produce many duplicated points when using the "Triangulate the slice" option, which is default.
SliceWithPlane has the same issue. Only with UG.
Steps to reproduce:
- Open ParaView
- UnstructuredCellTypes, Apply
- Slice, Ap...Slice filter produce many duplicated points when using the "Triangulate the slice" option, which is default.
SliceWithPlane has the same issue. Only with UG.
Steps to reproduce:
- Open ParaView
- UnstructuredCellTypes, Apply
- Slice, Apply, note that "Triangulate the mesh" and "merge duplicated point" options are both checked.
- Output contains 1167 points, way too many
- Clean, Apply
- Output contain 225 points, this would be the expected output
- Disabling the "Triangulate the mesh" option work around the issue.
FYI @will.schroeder @charles.gueunetCory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20492SliceWithPlane missing cell data with vtkImageData input2021-03-24T09:23:12-04:00Mathieu Westphal (Kitware)SliceWithPlane missing cell data with vtkImageData inputSliceWithPlane filter does not produce any cell data with vtkImageData input.
Steps to reproduce:
* Open ParaView
* Wavelet, Apply
* RandomAttributes, CellScalars, Apply
* SliceWithPlane, Apply
* No RandomCellScalars are present in the...SliceWithPlane filter does not produce any cell data with vtkImageData input.
Steps to reproduce:
* Open ParaView
* Wavelet, Apply
* RandomAttributes, CellScalars, Apply
* SliceWithPlane, Apply
* No RandomCellScalars are present in the slice
FYI @will.schroeder @charles.gueunethttps://gitlab.kitware.com/paraview/paraview/-/issues/20485Shortcut for doc broken when loading a plugin2021-06-23T12:55:30-04:00Nicolas VuailleShortcut for doc broken when loading a pluginThe ShowHelpForFilter feature is not working properly when a plugin is loaded.
The issue is present in v5.9.0.
Steps to reproduce:
- Open ParaView
- Create a wavelet, Apply
- Click on help button
- Help appears correctly
- close help
-...The ShowHelpForFilter feature is not working properly when a plugin is loaded.
The issue is present in v5.9.0.
Steps to reproduce:
- Open ParaView
- Create a wavelet, Apply
- Click on help button
- Help appears correctly
- close help
- Tools -> Manage plugin -> Load any plugin
- Click on help button
- Help appears empty
The following appears in the output message:
`warning: QTextBrowser: No document for qthelp://gmvreader.org/GMVReader/sources.RTAnalyticSource.html`
Actually, only the documentation of the last loaded plugin is working.
The doc is still accessible in the help menu of ParaView.
For some reasons, this warning does not appears when using QtWebEngine.
FYI @timothee.chabat @nicolas.vuaillehttps://gitlab.kitware.com/paraview/paraview/-/issues/20444seg fault running simple python script with mpi (5.9.0 RC4)2023-06-15T11:25:25-04:00Scott Wittenburgseg fault running simple python script with mpi (5.9.0 RC4)I downloaded release candidate binary for mac os (ParaView-5.9.0-RC4-MPI-OSX10.13-Python3.8-64bit.dmg), and then tried to run a simple python script, and it resulted in a segmentation fault.
Here is the `pvpython`/`pvbatch` script:
```...I downloaded release candidate binary for mac os (ParaView-5.9.0-RC4-MPI-OSX10.13-Python3.8-64bit.dmg), and then tried to run a simple python script, and it resulted in a segmentation fault.
Here is the `pvpython`/`pvbatch` script:
```python
import paraview.simple as simple
simple.servermanager.Connect("localhost")
print("connected")
cone = simple.Cone()
print("cone created")
```
Here are the steps to reproduce:
Start the server
```console
/Applications/ParaView-5.9.0-RC4.app/Contents/bin/pvserver --force-offscreen-rendering
```
Start the client
```console
/Applications/ParaView-5.9.0-RC4.app/Contents/bin/pvbatch ./client_script.py
```
Here's the output from the client:
```console
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
connected
Loguru caught a signal: SIGSEGV
Stack trace:
24 0x2 28 ??? 0x0000000000000002 0x0 + 2
23 0x7fff721b2cc9 start + 1
22 0x10fc99742 ParaViewPython::Run(int, int, char**) + 818
21 0x11026a91e vtkPythonInterpreter::PyMain(int, char**) + 558
20 0x111e2eb9b Py_Main + 43
19 0x111e2ed46 pymain_main + 406
18 0x111e2e77a Py_RunMain + 2234
17 0x111e0e76f PyRun_SimpleFileExFlags + 271
16 0x111e0f373 PyRun_FileExFlags + 291
15 0x111dbc1f0 PyEval_EvalCode + 48
14 0x111dc8223 _PyEval_EvalCodeWithName + 3459
13 0x111dc38bd _PyEval_EvalFrameDefault + 30253
12 0x111dc7092 call_function + 354
11 0x111ce056e _PyFunction_Vectorcall + 254
10 0x111dc8223 _PyEval_EvalCodeWithName + 3459
9 0x111dc38bd _PyEval_EvalFrameDefault + 30253
8 0x111dc7092 call_function + 354
7 0x111ce2f3b method_vectorcall + 171
6 0x111ce056e _PyFunction_Vectorcall + 254
5 0x111dc8223 _PyEval_EvalCodeWithName + 3459
4 0x111dc3e04 _PyEval_EvalFrameDefault + 31604
3 0x111ce00b3 cfunction_call_varargs + 323
2 0x12ac450b8 PyvtkSMParaViewPipelineController_RegisterPipelineProxy(_object*, _object*) + 504
1 0x10fd52c6a vtkSMParaViewPipelineController::RegisterPipelineProxy(vtkSMProxy*, char const*) + 442
0 0x4 4 ??? 0x0000000000000004 0x0 + 4
( 8.031s) [pvbatch ] :0 FATL| Signal: SIGSEGV
Segmentation fault: 11
```
Here's the output from the server:
```console
Waiting for client...
Connection URL: cs://Scotts-MacBook-Pro-2.local:11111
Accepting connection(s): Scotts-MacBook-Pro-2.local:11111
Client connected.
( 22.205s) [pvserver ]vtkSocketCommunicator.c:781 ERR| vtkSocketCommunicator (0x7fb044e19d80): Could not receive tag. 1
( 22.205s) [pvserver ]vtkTCPNetworkAccessMana:297 ERR| vtkTCPNetworkAccessManager (0x7fb044d117a0): Some error in socket processing.
( 22.205s) [pvserver ] vtkSocket.cxx:532 ERR| vtkClientSocket (0x7fb044e171b0): Socket error in call to send. Broken pipe.
( 22.205s) [pvserver ] vtkSocket.cxx:532 ERR| vtkClientSocket (0x7fb044e171b0): Socket error in call to send. Broken pipe.
...
( 22.319s) [pvserver ] vtkSocket.cxx:532 ERR| vtkClientSocket (0x7fb044e171b0): Socket error in call to send. Broken pipe.
Segmentation fault: 11
```
For brevity, in the server output above, I omitted many, many of those `Socket error in call to send. Broken pipe.` messages in favor of `...`.https://gitlab.kitware.com/paraview/paraview/-/issues/20434ParaView incorrectly pruning face when adjacent to invalid cells2021-03-24T08:54:42-04:00Utkarsh AyachitParaView incorrectly pruning face when adjacent to invalid cells* load attached [dataset_0_0.vti](/uploads/d6d9a7f2f0b4aef7a7270c7fafdbacac/dataset_0_0.vti).
* show as surface with edges...it renders hollow. It only have ghost cells on half of the missing face, others are flagged as invalid cells. th...* load attached [dataset_0_0.vti](/uploads/d6d9a7f2f0b4aef7a7270c7fafdbacac/dataset_0_0.vti).
* show as surface with edges...it renders hollow. It only have ghost cells on half of the missing face, others are flagged as invalid cells. those should not have been treated as external faces.
* apply tetrahedralize and the same issue persists.
Issues: ghost cells marked as invalid are being treated as duplicated ghost cells, which is incorrect.https://gitlab.kitware.com/paraview/paraview/-/issues/20430Memory leaks when resizing 2D views2021-03-24T08:55:15-04:00Timothee ChabatMemory leaks when resizing 2D viewsA lot of (2D) views have leaks when being resized. Compiling with `VTK_DEBUG_LEAKS=ON` detects no leaks at the end of the execution.
## Tested on master
### Leaking :
- Box chart
- Bar chart
- Histogram
- Line chart
- Parallel co...A lot of (2D) views have leaks when being resized. Compiling with `VTK_DEBUG_LEAKS=ON` detects no leaks at the end of the execution.
## Tested on master
### Leaking :
- Box chart
- Bar chart
- Histogram
- Line chart
- Parallel coordinates
- Python charts
- Point chart
- Quartile chart
### Not leaking :
- Render view
- Spreadsheet view
## Step to reproduce
- Open paraview and any of the views mentioned earlier.
- Resize by dragging the limit between the layout and the pipeline browser.
Loading / displaying data is not mandatory. It doesn't matter if the view is a new layout or not.https://gitlab.kitware.com/paraview/paraview/-/issues/20425ParaView uses internal headers from VTK2021-03-24T08:56:15-04:00Albert ZiegenhagelParaView uses internal headers from VTKOne part of the problem described in #19515 (making ParaView work with an external VTK installation) is that ParaView uses headers that are not installed by VTK.
One such example is the header `vtkCompositeZPassFS.h` used by ParaView he...One part of the problem described in #19515 (making ParaView work with an external VTK installation) is that ParaView uses headers that are not installed by VTK.
One such example is the header `vtkCompositeZPassFS.h` used by ParaView here:
https://gitlab.kitware.com/paraview/paraview/-/blob/510ee33bbc32de0882dd753fd8ceb61eb2a309ed/Remoting/Views/vtkIceTCompositePass.cxx#L50
and declared "private" by VTK here:
https://gitlab.kitware.com/vtk/vtk/-/blob/67fe537b6ee09b8c08bae8fd2bbc1311b29d05dd/Rendering/Parallel/CMakeLists.txt#L37
In `vcpkg` we do manually install such files with VTK to make building ParaView with an external VTK possible. See
https://github.com/microsoft/vcpkg/blob/9ddc9173d7858ddb40b2fc0cdc73b529c390ba47/ports/vtk/portfile.cmake#L295-L298
If you could point me to the best way to solve these issues, I would be more than glad to contribute in this field.
I thought having this problem as a separate issue from #19515 might help to tackle to problem in smaller steps, but feel free to close this issue as a duplicate if you disagree.https://gitlab.kitware.com/paraview/paraview/-/issues/20418Invalid reported time values with some OpenFoam data2021-03-24T08:56:41-04:00Sebastien JourdainInvalid reported time values with some OpenFoam data`simple.GetAnimationScene().TimeKeeper.TimestepValues` is not always reporting a list of values but a single time value instead (float vs [float]).
Initially reported [here](https://github.com/Kitware/paraviewweb/issues/524)`simple.GetAnimationScene().TimeKeeper.TimestepValues` is not always reporting a list of values but a single time value instead (float vs [float]).
Initially reported [here](https://github.com/Kitware/paraviewweb/issues/524)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20408glTF Exporter only export first block from multiblock2022-12-08T09:04:39-05:00Mathieu Westphal (Kitware)glTF Exporter only export first block from multiblockglTF Exporter only export first block from multiblock
Steps to reproduce:
* Open ParaView
* Open Can.ex2
* Export scene to glTF
* Visualize glTF in another tools
* Only first block is exported
@ken-martinglTF Exporter only export first block from multiblock
Steps to reproduce:
* Open ParaView
* Open Can.ex2
* Export scene to glTF
* Visualize glTF in another tools
* Only first block is exported
@ken-martinhttps://gitlab.kitware.com/paraview/paraview/-/issues/20397Background settings oddities2021-03-24T08:51:21-04:00Mathieu Westphal (Kitware)Background settings odditiesTwo oddities with the background setting saving:
1. Saving settings when not needed
* Open ParaView
* Click on "Save View Settings"
* Close ParaView
* Background settings is being saved in ParaView-UserSettings but has not been changed ...Two oddities with the background setting saving:
1. Saving settings when not needed
* Open ParaView
* Click on "Save View Settings"
* Close ParaView
* Background settings is being saved in ParaView-UserSettings but has not been changed by the user in any way, it should not
2. Saving single color settings doesn't have expected behavior
* Open ParaView
* Set a background color to not default (color1)
* Click on "Save View Settings"
* Close ParaView
* Open ParaView
* Edit->Settings->ColorPallette->Gradient
* Background is changed to a gradient using color1 and another color, this is unexpected.https://gitlab.kitware.com/paraview/paraview/-/issues/20394Slice Value Range doesn't update2022-11-01T22:06:00-04:00Andrew BauerSlice Value Range doesn't updateIn ParaView master (roughly around ParaView 5.9 release candidate 2) the `Value Range` is not properly updating for the `Slice` filter, even when clicking the `Reset using current data values` button (though I'm not sure if that's what t...In ParaView master (roughly around ParaView 5.9 release candidate 2) the `Value Range` is not properly updating for the `Slice` filter, even when clicking the `Reset using current data values` button (though I'm not sure if that's what that button is for). To reproduce the issue:
1. Create a Wavelet with Whole Extent [-10, 100, -10, 10, -10, 10]
2. Create a Slice filter
3. Click on the Y Normal
The `Value Range` should be [-17.3205, 17.3205], i.e. the values if the Wavelet Whole Extent was [-10, 10, -10, 10, -10, 10] but is instead [-56.7891,56.7891].Aron HelserAron Helserhttps://gitlab.kitware.com/paraview/paraview/-/issues/20385vtkRedistributeDataSet does not handle dataset without cells2021-03-24T08:51:28-04:00Utkarsh AyachitvtkRedistributeDataSet does not handle dataset without cellsIssue surfaced when debugging paraview/paraview#20382. Once fixed, make sure `vtkPointGaussianRepresentation` is updated to avoid creating of vertex-cells.Issue surfaced when debugging paraview/paraview#20382. Once fixed, make sure `vtkPointGaussianRepresentation` is updated to avoid creating of vertex-cells.https://gitlab.kitware.com/paraview/paraview/-/issues/20383XML Settings only proxy fails to build because of automatic documentation gen...2021-03-24T08:52:08-04:00Mathieu Westphal (Kitware)XML Settings only proxy fails to build because of automatic documentation generationA plugin containing only a `<SettingsProxy>` fails to build with the following error:
```
<ParaViewPlugin>
<ServerManagerConfiguration>
<ProxyGroup name="settings">
<SettingsProxy name="PacManSettings" label="PacMan"
...A plugin containing only a `<SettingsProxy>` fails to build with the following error:
```
<ParaViewPlugin>
<ServerManagerConfiguration>
<ProxyGroup name="settings">
<SettingsProxy name="PacManSettings" label="PacMan"
processes="client|dataserver|renderserver">
<Documentation>
Settings for the PacMan plugin.
</Documentation>
<IntVectorProperty name="TestOption"
number_of_elements="1"
default_values="0">
<Documentation>
This is a simple boolean test option.
</Documentation>
<BooleanDomain name="bool" />
</IntVectorProperty>
<Hints>
<UseDocumentationForLabels />
</Hints>
</SettingsProxy>
</ProxyGroup>
</ServerManagerConfiguration>
</ParaViewPlugin>
```
```
[ 42%] Compiling Qt help for ReaderXMLOnly
CMake Error at /home/glow/work/paraview/pv3/build/lib/cmake/paraview-5.9/ParaViewClient.cmake:892 (message):
No matching files given without a table of contents
make[2]: *** [Plugin/CMakeFiles/ReaderXMLOnly_qch.dir/build.make:80: Plugin/paraview_help/ReaderXMLOnly.qch] Error 1
make[1]: *** [CMakeFiles/Makefile2:145: Plugin/CMakeFiles/ReaderXMLOnly_qch.dir/all] Error 2
make: *** [Makefile:149: all] Error 2
```
Adding a single dummy `<SourceProxy>` fixes the issue.
Attached is an example to reproduce easily.
[ReaderXMLOnly.tgz](/uploads/bada628f85e7342849d24e1823e8b656/ReaderXMLOnly.tgz)