static builds of paraview search for plugin shared libs on startup (#19460) · Issues · ParaView / ParaView

static builds of paraview search for plugin shared libs on startup

For a static build of ParaView, run as follows:

> env PARAVIEW_LOG_PLUGIN_VERBOSITY=INFO ./bin/pvpython -dr

You'll see output as follows:

...
(   0.334s) [paraview        ] vtkPVPluginTracker.cxx:405   INFO| Trying to locate plugin with name `VTKmFilters`
(   0.334s) [paraview        ] vtkPVPluginTracker.cxx:105   INFO| { looking for plugin 'VTKmFilters'
(   0.334s) [paraview        ]vtkResourceFileLocator.:61    INFO| .   { looking for 'VTKmFilters.so'
...

This implies that ParaView is wasting time attempting to find files for plugins to load which are never present or loadable in static builds. This should be fixed to improve HPC performance.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information