# paraview built from source crashes loading silo file

**URL:** https://discourse.paraview.org/t/paraview-built-from-source-crashes-loading-silo-file/13242
**Category:** ParaView Support
**Created:** [November 12, 2023, 5:16am UTC](https://discourse.paraview.org/t/paraview-built-from-source-crashes-loading-silo-file/13242 "2023-11-12T05:16:25Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![kmilo9999](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/k/cc9497/32.png) [@kmilo9999](https://discourse.paraview.org/u/kmilo9999)
#### Post date: [November 12, 2023, 5:16am UTC](https://discourse.paraview.org/t/paraview-built-from-source-crashes-loading-silo-file/13242/1 "2023-11-12T05:16:25Z")

</div>

Hi all.

I am using Paraview 5.11 that I built from source in a linux cluster. I have some silo files and in order to read load them in Paraview, I configured the cmake file enabling the options PARAVIEW\_USE\_VISITBRIDGE and VISIT\_BUILD\_READER\_Silo

I tested with multiple silo files and it seems to work with some datasets, but it crashes with others ([this one](https://software.llnl.gov/Silo/ghpages/examples/amr3d_wmrgtree.silo) for example) Here is the error log:

> ERROR: In vtkVisItSiloReader.cxx, line 135  
> vtkVisItSiloReader (0xa29a950): There was an error opening /data/light/amr3d\_wmrgtree.silo. It may be an invalid file.
> 
> ERROR: In vtkExecutive.cxx, line 740  
> vtkPVCompositeDataPipeline (0xb8931c0): Algorithm vtkFileSeriesReader (0x9741770) returned failure for request: vtkInformation (0x86fdcf0)  
> Debug: Off  
> Modified Time: 3483136  
> Reference Count: 1  
> Registered Events: (none)  
> Request: REQUEST\_DATA\_OBJECT  
> ALGORITHM\_AFTER\_FORWARD: 1

Loading this dataset in a prebuild Paraview 5.11 executable loads the file without any issues.

Any thoughts ? Thank you for the help in advance.

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [November 13, 2023, 8:38am UTC](https://discourse.paraview.org/t/paraview-built-from-source-crashes-loading-silo-file/13242/2 "2023-11-13T08:38:23Z")

</div>

I confirm that there is a regression between 5.11.1 and master. Please open an issue here:  
[https://gitlab.kitware.com/paraview/paraview/-/issues](https://gitlab.kitware.com/paraview/paraview/-/issues)

Ideally, since you are able to build paraview, you could bisect ParaView/VTK/ViSit to identify the commit causing the regression.

---

<div class="post-metadata">

### Author: ![kmilo9999](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/k/cc9497/32.png) [@kmilo9999](https://discourse.paraview.org/u/kmilo9999)
#### Post date: [November 13, 2023, 3:12pm UTC](https://discourse.paraview.org/t/paraview-built-from-source-crashes-loading-silo-file/13242/3 "2023-11-13T15:12:07Z")

</div>

Hello Mathieu,  
Thank you for checking this. Is it possible for you to help me pointing me to the specific commit?

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [November 13, 2023, 3:15pm UTC](https://discourse.paraview.org/t/paraview-built-from-source-crashes-loading-silo-file/13242/4 "2023-11-13T15:15:24Z")

</div>

> Is it possible for you to help me pointing me to the specific commit?

Well, no. I’m suggesting that you could bisect to find out which commit causes it.

---

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [November 17, 2023, 3:29am UTC](https://discourse.paraview.org/t/paraview-built-from-source-crashes-loading-silo-file/13242/5 "2023-11-17T03:29:42Z")

</div>

I see this issue: [https://gitlab.kitware.com/paraview/paraview/-/issues/22373](https://gitlab.kitware.com/paraview/paraview/-/issues/22373)