# Paraview 5.8 segmentation fault at start on CentOS 7 only after building OpenFOAM-v2006

**URL:** https://discourse.paraview.org/t/paraview-5-8-segmentation-fault-at-start-on-centos-7-only-after-building-openfoam-v2006/5464
**Category:** ParaView Support
**Created:** [October 1, 2020, 10:02am UTC](https://discourse.paraview.org/t/paraview-5-8-segmentation-fault-at-start-on-centos-7-only-after-building-openfoam-v2006/5464 "2020-10-01T10:02:09Z")
**Posts on this page:** 1
**Showing post:** 11

<div class="post-metadata">

### Author: ![Root-voidX](https://discourse.paraview.org/user_avatar/discourse.paraview.org/root-voidx/32/5084_2.png) [@Root-voidX](https://discourse.paraview.org/u/Root-voidX)
#### Post date: [October 1, 2020, 9:56pm UTC](https://discourse.paraview.org/t/paraview-5-8-segmentation-fault-at-start-on-centos-7-only-after-building-openfoam-v2006/5464/11 "2020-10-01T21:56:00Z")

</div>

It definitely seems using module purge to unload openmpi system module worked, since I can start Paraview Binary. However it seems I do need the openmpi module to be loaded for openfoam and other software which I plan on building (SU2, Elmer). For now I just using a bashrc function as a workaround:

> function paraview {  
> module purge;  
> /home/CentOS-VM/.root/opt/ParaView-5.8.1-MPI-Linux-Python3.7-64bit/bin/paraview  
> module load mpi/openmpi-x86\_64;  
> };

As this could call paraview using this function name, and when I quit, it automatically loads mpi module again. Only downside is I cant use paraFoam, gotta use touch .foam to create a file and then run paraview.

---

_[View the full topic](https://discourse.paraview.org/t/paraview-5-8-segmentation-fault-at-start-on-centos-7-only-after-building-openfoam-v2006/5464)._