# Linux 4.10.1 volume rendering crash issue

**URL:** <https://discourse.slicer.org/t/linux-4-10-1-volume-rendering-crash-issue/5554>\
**Category:** Support\
**Created:** [January 29, 2019, 4:36am UTC](https://discourse.slicer.org/t/linux-4-10-1-volume-rendering-crash-issue/5554 "2019-01-29T04:36:10Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![muratmaga](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/muratmaga/32/3622_2.png) [@muratmaga](https://discourse.slicer.org/u/muratmaga)\
**Post date:** [January 29, 2019, 4:36am UTC](https://discourse.slicer.org/t/linux-4-10-1-volume-rendering-crash-issue/5554/1 "2019-01-29T04:36:11Z")

</div>

Trying to open a previously saved mrb, Slicer crashes with this error.

SlicerApp-real[46207]: segfault at 0 ip 00002aab9bc04c4e sp 00007fffffffad30 error 4 in libvtkSlicerVolumeRenderingModuleLogic.so[2aab9bbf9000+15000]

Anyway to understand what’s causing it? This is on Centos 7.2 with slicer 4.10.1

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [January 29, 2019, 7:56am UTC](https://discourse.slicer.org/t/linux-4-10-1-volume-rendering-crash-issue/5554/2 "2019-01-29T07:56:37Z")

</div>

Hi Murat -

Dp you think it’s the file or the machine? Does the same mrb open on a different machine/os? Can you create a new mrb on that machine and reproduce the issue?

---

<div class="post-metadata">

**Author:** ![muratmaga](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/muratmaga/32/3622_2.png) [@muratmaga](https://discourse.slicer.org/u/muratmaga)\
**Post date:** [January 29, 2019, 4:39pm UTC](https://discourse.slicer.org/t/linux-4-10-1-volume-rendering-crash-issue/5554/3 "2019-01-29T16:39:55Z")

</div>

It must be the mrb and data it contains. It also crashes on windows or get stuck at 52% if I unpack the contents of the mrb file and load the top level mrml.

We created this scene file, and all other mrbs also created on the same installation of Slicer seems to work fine. Weird.