ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-12-04T15:53:39-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/22407Feature: add ability to specify which representations are included in camera ...2023-12-04T15:53:39-05:00Cory Quammencory.quammen@kitware.comFeature: add ability to specify which representations are included in camera Reset actionAdd a way, only in Python is okay, to reset the view to ensure a select list of representations is centered in the view.Add a way, only in Python is okay, to reset the view to ensure a select list of representations is centered in the view.https://gitlab.kitware.com/paraview/paraview/-/issues/22406CAVEInteraction: let roles be listed in order declared in Python interactor s...2023-12-04T15:43:02-05:00Cory Quammencory.quammen@kitware.comCAVEInteraction: let roles be listed in order declared in Python interactor script and not alphabetized5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22405CAVEInteraction: in Python interactor, object/attribute pulldowns should be b...2023-12-04T14:56:19-05:00Cory Quammencory.quammen@kitware.comCAVEInteraction: in Python interactor, object/attribute pulldowns should be blankAccess to all proxies and their properties is already available within the script.Access to all proxies and their properties is already available within the script.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22402ResetSession() breaks GetLayout()2024-03-27T08:01:49-04:00baloeResetSession() breaks GetLayout()running the following through `pvbatch`
```python
from paraview.simple import *
renderView1 = GetActiveViewOrCreate('RenderView')
layout1 = GetLayout()
print(layout1)
ResetSession()
renderView1 = GetActiveViewOrCreate('RenderView')
la...running the following through `pvbatch`
```python
from paraview.simple import *
renderView1 = GetActiveViewOrCreate('RenderView')
layout1 = GetLayout()
print(layout1)
ResetSession()
renderView1 = GetActiveViewOrCreate('RenderView')
layout1 = GetLayout()
print(layout1)
```
prints
```
<paraview.servermanager.ViewLayout object at 0x7f841067ffd0>
None
```
I am expecting another Viewlayout reference instead of that None in the second line.
This renders `ResetSession()` useless for me right now, and I have needed `ResetSession()` in the past to mitigate memory leakage issues when iterating over time steps. So I think it is a feature worth having just in case.https://gitlab.kitware.com/paraview/paraview/-/issues/22401Superbuild is failing using system python2024-02-07T07:46:44-05:00W. Alan ScottSuperbuild is failing using system pythonSuperbuild is failing using system python. The issue is pythonwheel is trying to be built and installed, and the install is trying to update the system. We don't have permission to write into system Python. Thus, the build breaks.
I ...Superbuild is failing using system python. The issue is pythonwheel is trying to be built and installed, and the install is trying to update the system. We don't have permission to write into system Python. Thus, the build breaks.
I have given detailed information to Ben offline.
This doesn't impact ParaView itself, but rather memory footprint for Catalyst.
@ben.boeckel5.12.1 (Spring 2024)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/22400Default readers not honored on MacOS2024-03-07T20:18:17-05:00Nathan WoodsDefault readers not honored on MacOSRelated to this Discourse: https://discourse.paraview.org/t/default-reader-not-honored-when-loading-exodus-file/13387/7
When multiple readers are available for a given file, Paraview prompts the user to select the appropriate one. The G...Related to this Discourse: https://discourse.paraview.org/t/default-reader-not-honored-when-loading-exodus-file/13387/7
When multiple readers are available for a given file, Paraview prompts the user to select the appropriate one. The GUI presents an option to set this as the default reader for that file type. On Windows and Linux, future instances of Paraview automatically use the default reader without prompting a user selection. On MacOS, it is not apparent that the choice of default reader has any effect at all.
To reproduce (on MacOS):
- Open a file with more than one allowable reader (we tested with IOSS/Legacy Exodus).
- Choose the appropriate reader and "Set reader as default".
- Restart Paraview
- Open the same file to be prompted again to choose the reader5.12.1 (Spring 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22398ParaViewExample-Catalyst2/PythonFullExample Test is flaky on fedora static CI2023-12-23T01:53:10-05:00Mathieu Westphal (Kitware)ParaViewExample-Catalyst2/PythonFullExample Test is flaky on fedora static CIParaViewExample-Catalyst2/PythonFullExample Test is flaky on fedora static CI
![a](/uploads/92deafad7c52489880baca0c99955f79/a.png)
The test is being exluded here: https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6607ParaViewExample-Catalyst2/PythonFullExample Test is flaky on fedora static CI
![a](/uploads/92deafad7c52489880baca0c99955f79/a.png)
The test is being exluded here: https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6607https://gitlab.kitware.com/paraview/paraview/-/issues/22396`--connect-id` argument with a value > int32 max fails with unhelpfull error2023-12-04T08:15:19-05:00Mathieu Westphal (Kitware)`--connect-id` argument with a value > int32 max fails with unhelpfull errorThe following command fails with:
```
> ./bin/paraview --connect-id 2147483648
Could not convert: --connect-id = 2147483648
Usage: /home/glow/dev/paraview/others/ParaView-5.11.1-MPI-Linux-Python3.9-x86_64/bin/paraview-real [OPTIONS]
[...The following command fails with:
```
> ./bin/paraview --connect-id 2147483648
Could not convert: --connect-id = 2147483648
Usage: /home/glow/dev/paraview/others/ParaView-5.11.1-MPI-Linux-Python3.9-x86_64/bin/paraview-real [OPTIONS]
[General Guidelines]
Values for options can be specified either with a space (' ') or an equal-to sign ('='). Thus, '--option=value' and '--option
value' are equivalent.
Multi-valued options can be specified by providing the option multiple times or separating the values by a comma (','). Thus,
'--moption=foo,bar' and '--moption=foo --moption=bar' are equivalent.
Short-named options with more than one character name are no longer supported, and should simply be specified as long-named option
by adding an additional '-'. Thus, use '--dr' instead of '-dr'.
Some options are described in this help text with the format '--moption TYPE:name' where 'TYPE' specifies what kind of value is
expected for the option 'name'. Type 'ENUM' means there are several possible predefined values for the option. Type 'TEXT' means
that the filename option is any text string.
Numeric specifiers 'INT' and 'FLOAT' in this help text indicate the expected option value type of some options, either an integer
or floating point number.
Try `--help` for more more information.
```
The error message is unclear (and actually misleading, because it mentions formatting but `=` was never used although it makes look like it was).
The reason for this to not work is because 2147483648 > int max.
A better error message would help users.https://gitlab.kitware.com/paraview/paraview/-/issues/22395Improve ParaView settings files organization2024-03-25T16:34:11-04:00Nicolas VuailleImprove ParaView settings files organizationI think we can improve the way ParaView stores settings. Here is the typical content of the user settings directory:
```
> ls .config/ParaView
d Macros
d Icons
ParaView5.10.1.ini
ParaView5.11.1-dr.ini
ParaView5.11.1.ini
ParaView...I think we can improve the way ParaView stores settings. Here is the typical content of the user settings directory:
```
> ls .config/ParaView
d Macros
d Icons
ParaView5.10.1.ini
ParaView5.11.1-dr.ini
ParaView5.11.1.ini
ParaView5.11.2.ini
ParaView5.12.0-dr.ini
ParaView5.12.0.ini
ParaView.conf
ParaView-UserSettings.json
d PythonSwap
d Scripts
servers.pvsc
```
Here are different questions about that:
1. `--dr` means disable registry, i.e. "do not load settings". So is `ParaView<version>-dr.ini` really needed ?
2. `ParaView.conf` is the file created when using default `pqSettings` instance instead of the one configured by the ParaView application. So I think it should not be there (and here is a related MR to remove this file: https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6602)
3. `.ini` files are version-dependent, while `.json` is not. Is that truly intended ?
4. Using a newer version of ParaView for the first time does not reuse at all older settings. So keeping preference requires manual operation. (for instance custom shortcuts, default UI configuration and so)
5. `.json` seems to be *proxies/properties default values* while `.ini` is more *interface stuff*, but not sure if it is documented somewhere.https://gitlab.kitware.com/paraview/paraview/-/issues/22391Right click menu context is incorrect2024-03-07T20:23:59-05:00W. Alan ScottRight click menu context is incorrectThe right click menu context is incorrect. Please check all menu items. Here is a trivial replicator for Edit Color.
* 5.12.0-RC1, Windows, builtin server.
* Sources/ Box. Apply.
* Sources/ Box. Center 1.2, 0, 0. Apply.
* Reset.
* R...The right click menu context is incorrect. Please check all menu items. Here is a trivial replicator for Edit Color.
* 5.12.0-RC1, Windows, builtin server.
* Sources/ Box. Apply.
* Sources/ Box. Center 1.2, 0, 0. Apply.
* Reset.
* Right mouse click on the left box. This one is the first box, and is NOT selected in the pipeline browser.
* Edit Color. Black. OK.
The right block changes to black. This is a bug.
![image](/uploads/1fba9f9530cd0ab423e4b78884f86fe3/image.png)5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22389Paraview 5.12.0-RC1: Loading State File Error for vtkAppendSelection in Paral...2024-03-07T20:23:59-05:00Zongze YangParaview 5.12.0-RC1: Loading State File Error for vtkAppendSelection in Parallel Server when Using State File Created with `Find Data` and `Plot Over Time`The encountered error is as follows:
```
ERROR: In vtkDemandDrivenPipeline.cxx, line 677
vtkPVCompositeDataPipeline (0x600005419f00): Input port 0 of algorithm vtkAppendSelection (0x600005627c00) has 0 connections but is not optional.
`...The encountered error is as follows:
```
ERROR: In vtkDemandDrivenPipeline.cxx, line 677
vtkPVCompositeDataPipeline (0x600005419f00): Input port 0 of algorithm vtkAppendSelection (0x600005627c00) has 0 connections but is not optional.
```
However, it appears that this error does not impact the rendering results.
## Steps to Reproduce the Issue:
1. Initiate the server (optional):
```bash
mpiexec -n 2 pvserver
```
2. Load the file `can.ex2` (Examples -> can.ex2)
3. Navigate to View -> Find Data:
Locate the point (4, 4, 1) with a tolerance of 1, and then proceed to `Plot Over Time`.
4. Save the state. (The state files are attached.)
The error consistently manifests when using the state file in conjunction with the mpi-server, irrespective of whether the state file was created with or without the mpi-server.
[test-mpi2.pvsm](/uploads/90562b4c7d2a365bb3efa7d09be7a71b/test-mpi2.pvsm)
[test-nompi.pvsm](/uploads/3662d6a453176671d9a3b584ea3036f1/test-nompi.pvsm)5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22386Color by Scalar broken on Line Width greater 12023-12-07T16:35:46-05:00Johannes GrossColor by Scalar broken on Line Width greater 1OS: macOS 13.0
ParaView Version: 5.11.2
Qt Version: 5.15.2
Description
I am trying to show a mass flow in pipes in the appended file.
When setting to Wireframe and using massflow for the color scheme, the flows are displayed fairly cor...OS: macOS 13.0
ParaView Version: 5.11.2
Qt Version: 5.15.2
Description
I am trying to show a mass flow in pipes in the appended file.
When setting to Wireframe and using massflow for the color scheme, the flows are displayed fairly correct (some pipes do not show the red color although they should) but once the Line Width is set to any number greater 1 the colors are all over the place. Line elements that have value 0 are shown in red, Pipe Elements with higher values are shown in blue. I hope this is not some rookie mistake on my end but the file seems fairly simple and straightforward, could not find any other explanation for the issue. Thank you!
[helloagain2.vtk](/uploads/15fb1563971cc7f65c6a21d91f84f52c/helloagain2.vtk)https://gitlab.kitware.com/paraview/paraview/-/issues/22385ParaView 5.12.0-RC1: non-responsive floating windows : ‘Output Messages’ and ...2024-03-07T20:23:59-05:00Lourenço Sassetti MendesParaView 5.12.0-RC1: non-responsive floating windows : ‘Output Messages’ and ‘Choose Preset’This occurs using WSL2, under Windows 11, using both Ubuntu 22.04 and OpenSuse 15.5. It’s very easy to replicate.
It has nothing to do with specific states or files. Also occurs with “paraview --dr”.
1) The ‘Output Messages’ window when...This occurs using WSL2, under Windows 11, using both Ubuntu 22.04 and OpenSuse 15.5. It’s very easy to replicate.
It has nothing to do with specific states or files. Also occurs with “paraview --dr”.
1) The ‘Output Messages’ window when undocked, can’t be docked any more or resized, but it's still possible to close or select the checkboxes. If it pops up automatically, while using ParaView, it becomes completely non-responsive. The only option is to close it in the ‘View’ menu. It’s annoying because you’re not able to choose where it will pop up. The only way I found to dock it again is resetting ParaView: ‘Edit’ > ‘Reset To Default Settings’ and restart ParaView. This issue occurs both in versions 5.11.2 and 5.12.0.
2) In v5.12.0, the ‘Color Map Editor’ > ‘Choose Preset’ window is always non-responsive to mouse events, and even with TAB you can’t move to all checkboxes. It gets stuck in the default color presets table displayed, and you can’t select the other groups of presets (linear, diverging, etc). This issue occurs only in version 5.12.0.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22384ParaView 5.12-RC1 uses `~/.local` folder for python library instead of bundle...2024-03-29T08:25:09-04:00Francois MazenParaView 5.12-RC1 uses `~/.local` folder for python library instead of bundled python libsUsing the binary release of 5.12-RC1 of ParaView, it looks like the internal python runtime uses libraries from `~/.local` instead of the libraries available in the ParaView installation folder.
It's visible for the matplotlib path in t...Using the binary release of 5.12-RC1 of ParaView, it looks like the internal python runtime uses libraries from `~/.local` instead of the libraries available in the ParaView installation folder.
It's visible for the matplotlib path in the about dialog:
![image](/uploads/397b510ffe2eb436cacfad8d78fe9335/image.png)
When I remove my `~/.local` folder the expected lib is loaded:
![image](/uploads/478369cc715d4154b05895929bdb31ad/image.png)
When using the local libraries, it creates weird errors when using the FindData panel:
```
Error: Failed to evaluate Expression '(mag(B_A) == 0)'. The following exception stack should provide additional developer specific information. This typically implies a malformed expression. Verify that the expression is valid.
Warning: In vtkPythonSelector.cxx, line 104
vtkPythonSelector (0xa2d9380): Could not invoke 'python_selector.execute()'
Traceback (most recent call last):
File "/home/francois/Documents/Paraview/ParaView-5.12.0-RC1-MPI-Linux-Python3.10-x86_64/lib/python3.10/site-packages/paraview/detail/python_selector.py", line 80, in execute
maskArray = calculator.compute(inputs, query, ns=elocals)
File "/home/francois/Documents/Paraview/ParaView-5.12.0-RC1-MPI-Linux-Python3.10-x86_64/lib/python3.10/site-packages/paraview/detail/calculator.py", line 167, in compute
retVal = eval(subEx, globals(), mylocals)
File "<string>", line 1, in <module>
NameError: name 'B_A' is not defined
Generic Warning: In vtkSelection.cxx, line 752
No values to evaluate because there was an error in the selection evaluator.
ERROR: In vtkExecutive.cxx, line 729
vtkPVCompositeDataPipeline (0x8dd5320): Algorithm vtkPVExtractSelection (0x94b0d50) returned failure for request: vtkInformation (0xa2b9b70)
Debug: Off
Modified Time: 1243144
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA
FROM_OUTPUT_PORT: 0
ALGORITHM_AFTER_FORWARD: 1
FORWARD_DIRECTION: 0
```
I can't reproduce this issue with official binary of 5.11.0.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22381Error message if there is a Client/Server miss-match is reversed.2024-03-07T20:23:57-05:00Phil SmithError message if there is a Client/Server miss-match is reversed.If the Client and Server try and connect using different versions of ParaView, the error message is opposite of what it should be. It is reporting the client as the server and the server as the client. Please see the error below for an e...If the Client and Server try and connect using different versions of ParaView, the error message is opposite of what it should be. It is reporting the client as the server and the server as the client. Please see the error below for an example. Notice that the Client reports as version 5.11, however, I started version 5.12 as the client. I discovered the server was at 5.11, and that was the problem.
This is version 5.12.0-RC1-kw of ParaView.
PV_INSTALL_DIR is /snip/5.12.0-RC1-kw/Linux-cee-rhel7-x86_64
[1] 97892
Rendering in Hardware!
VisRTX 0.1.6, using devices:
0: GRID V100S-4Q (Total: 4.3 GB, Available: 2.6 GB)
Accepting connection(s): snip:11111
Accepting connection(s): snip:11111
( 284.763s) [paraview ]vtkTCPNetworkAccessMana:553 ERR| vtkTCPNetworkAccessManager (0xba7450): Client and server are different ParaView versions. Client reports version: 5.11 but server is version 5.12
( 284.767s) [paraview ]vtkTCPNetworkAccessMana:322 ERR| vtkTCPNetworkAccessManager (0xba7450):
**********************************************************************
Connection failed during handshake. The server has a different ParaView version than the client.
**********************************************************************5.13 (Summer 2024)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/22380ParaView installation with Kits and a module requiring a 3rd Party (FFMPEG) f...2024-03-21T08:50:01-04:00Eloise BParaView installation with Kits and a module requiring a 3rd Party (FFMPEG) fails to be configured againstBuilding and installing ParaView with Kits and enabling a module requiring a thied party dependency prevent any plugin or paraview based app to be configured against.
Steps to reproduce:
```
cd $path
git clone https://gitlab.kitware.co...Building and installing ParaView with Kits and enabling a module requiring a thied party dependency prevent any plugin or paraview based app to be configured against.
Steps to reproduce:
```
cd $path
git clone https://gitlab.kitware.com/paraview/paraview.git src
cd src
git submodule update --init --recursive
mkdir ../build
mkdir ../install
cd ../build
cmake -GNinja -DPARAVIEW_BUILD_WITH_KITS=ON -DPARAVIEW_ENABLE_FFMPEG -DCMAKE_INSTALL_PREFIX=../install ../src
ninja install
cd ../src/Examples/Plugins/ElevationFilter
mkdir build
cmake -DParaView_DIR=$path/install/lib/cmake/paraview-5.12/ ../
```
Fails with:
```
CMake Error at /home/glow/dev/paraview/pv1/install/lib/cmake/paraview-5.12/vtk/VTK-targets.cmake:5568 (set_target_properties):
The link interface of target "VTK::IOFFMPEG-objects" contains:
FFMPEG::avformat
but the target was not found. Possible reasons include:
* There is a typo in the target name.
* A find_package call is missing for an IMPORTED target.
* An ALIAS target is missing.
Call Stack (most recent call first):
/home/glow/dev/paraview/pv1/install/lib/cmake/paraview-5.12/vtk/vtk-config.cmake:149 (include)
/home/glow/dev/paraview/pv1/install/lib/cmake/paraview-5.12/paraview-config.cmake:77 (find_package)
CMakeLists.txt:4 (find_package)
```
Please note the recent introduction of `NO_KIT_EXPORT_IF_SHARED` did NOT fix the issue: https://gitlab.kitware.com/vtk/vtk/-/merge_requests/10929
==============================
Was: build of paraview based application with ffmpeg failed
Hello,
I have a paraview based application and I want to add ffmpeg support in it (to save avi format).
I build my application on top of paraview master with spack.
The build of paraview with ffmpeg succeed and I can export file in avi format (thanks to @ben.boeckel).
However, I can't build my application because it does not find ffmpeg:
```
>> 215 CMake Error at /home/billae/install_develop/spackinstaller/spack/opt/spack/linux-ubuntu23.04-skylake/gcc-13.1.0/paraview-master-lgzicckwpmphngih3wmnut4ldg73jlnb/
lib/cmake/paraview-5.12/vtk/VTK-targets.cmake:4761 (set_target_properties):
216 The link interface of target "VTK::IOFFMPEG-objects" contains:
217
218 FFMPEG::avformat
219
220 but the target was not found. Possible reasons include:
221
```
I tried differents CMAKE flags to give the path to ffmpeg in the config phase of my app (```-DFFMPEG_DIR```, ```-DFFMPEG_ROOT```, ```-DFFMPEG_LIBAVFORMAT_LIBRARIES```, ```-DFFMPEG_LIBAVFORMAT_INCLUDE```, ```-DCMAKE_MODULE_PATH```, ```-DCMAKE_PREFIX_PATH```) or to add a ```find_package``` to ffmpeg in my app, but nothing seems to help.
If anyone has an idea ? @westphalmhttps://gitlab.kitware.com/paraview/paraview/-/issues/22379Allow midpoints of color maps to be adjusted with adjacent points being moved2023-11-27T13:41:28-05:00W. Alan ScottAllow midpoints of color maps to be adjusted with adjacent points being movedHere is a proposal from Ken Moreland. Great idea, and it is needed as we add a new default color map. In essence, allow adjustment of control points in the color map editor to proportionally scale all other control points. Keep the ori...Here is a proposal from Ken Moreland. Great idea, and it is needed as we add a new default color map. In essence, allow adjustment of control points in the color map editor to proportionally scale all other control points. Keep the original behavior as an option. Make the new behavior the default.
From Ken:
To follow up on Francesca’s description of moving the midpoint of the colormap, I suggested a slightly more general feature. The idea would be that you would be able to adjust a control point such that the remaining control points would be proportionally scaled with respect to that point. The main use case would be to change the center point as Francesca suggests, but it would work with any control point.
To make the idea clearer, here is an example. Let’s say you have a colormap with 7 evenly spaced control points. Now let’s say you grab the middle control point (the 4th one) and move it to the left. The rest of the control points stay exactly where they are, and the movement of the middle point is constrained to be between the 3rd and 5th point. To really adjust the color map to move the “middle point” from the center of the range, you must independently adjust all the control points, which is problematic even with only 7. What we would like is an alternate move mode where when I move the 4th control point to the left, the 2nd and 3rd control points move closer together and left so that points 1, 2, 3, and 4 remain evenly spaced. Likewise, the 5th and 6th control points move further apart and left so that points 4, 5, 6, and 7 remain evenly spaced.
@kmorel5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22378Decimator causes crash2023-11-27T15:29:29-05:00Pavel JiranekDecimator causes crashOS: Windows 10 Version 2009
ParaView Version: 5.10.1
Qt Version: 5.15.2
Hello,
I have [this surface mesh](/uploads/358e9c5cf4c119d297f6794c8e0fb67d/poly.stl) I would like to decimate to have guaranteed number of triangles. However, I'm...OS: Windows 10 Version 2009
ParaView Version: 5.10.1
Qt Version: 5.15.2
Hello,
I have [this surface mesh](/uploads/358e9c5cf4c119d297f6794c8e0fb67d/poly.stl) I would like to decimate to have guaranteed number of triangles. However, I'm running into some troubles using the `vtkDecimatePro` filter and was able to reproduce the issue in ParaView. In fact, using the "Decimate" filter with
- target reduction set to 0.9,
- preservation of topology off,
- feature angle 15 degrees,
- boundary vertex deletion on,
makes the program crash. I was able to locate the issue to `vtkCellLinks::RemoveCellReference` which is called with `ptId` argument -1 which seems to be caused by `vtkDecimatePro::FindSplit` returning nonnegative value but both `pt1` and `pt2` equal to -1. Other than that I was not really able to do really any progress with this.
I'd highly appreciate any feedback with the issue. In my code, I'm using the latest 9.3.0 release of VTK with the same problem.
Cheers,
PavelSpiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22377FFMPEG Writer: test the FileName proxy setting2023-12-04T06:32:41-05:00Ben BoeckelFFMPEG Writer: test the FileName proxy settingBeing added in !6590.
Cc: @mwestphalBeing added in !6590.
Cc: @mwestphalBen BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/22373Paraview 5.11 crashes loading silo file2023-11-17T02:17:43-05:00kmilo9999Paraview 5.11 crashes loading silo fileAs explained in [discourse forum](https://discourse.paraview.org/t/paraview-built-from-source-crashes-loading-silo-file/13242/3). Some [Silo files ](https://software.llnl.gov/Silo/ghpages/examples/amr3d_wmrgtree.silo)make Paraview5.11 cr...As explained in [discourse forum](https://discourse.paraview.org/t/paraview-built-from-source-crashes-loading-silo-file/13242/3). Some [Silo files ](https://software.llnl.gov/Silo/ghpages/examples/amr3d_wmrgtree.silo)make Paraview5.11 crash. I built it from source and enabled PARAVIEW_USE_VISITBRIDGE and VISIT_BUILD_READER_Silo in the cmake configuration to read silo files.
Steps to reproduce:
* run ParaView
* open this \[file\](https://software.llnl.gov/Silo/ghpages/examples/amr3d_wmrgtree.silo), Apply
* segfault
It is a reggression between 5.11.0 and 5.12.0, should be bisected