# Segmentation fault. Loguru caught a signal: SIGSEGV

**URL:** https://discourse.paraview.org/t/segmentation-fault-loguru-caught-a-signal-sigsegv/11148
**Category:** ParaView Support
**Created:** [January 10, 2023, 8:54pm UTC](https://discourse.paraview.org/t/segmentation-fault-loguru-caught-a-signal-sigsegv/11148 "2023-01-10T20:54:32Z")
**Posts on this page:** 5
**Page:** 2

<div class="post-metadata">

### Author: ![spyridon97](https://discourse.paraview.org/user_avatar/discourse.paraview.org/spyridon97/32/11569_2.png) [@spyridon97](https://discourse.paraview.org/u/spyridon97)
#### Post date: [January 22, 2023, 11:24pm UTC](https://discourse.paraview.org/t/segmentation-fault-loguru-caught-a-signal-sigsegv/11148/21 "2023-01-22T23:24:13Z")

</div>

Segfaults? I have not seen something like that. Would you mind reporting such issue?

---

<div class="post-metadata">

### Author: ![jaswantp](https://discourse.paraview.org/user_avatar/discourse.paraview.org/jaswantp/32/11456_2.png) [@jaswantp](https://discourse.paraview.org/u/jaswantp)
#### Post date: [January 22, 2023, 11:29pm UTC](https://discourse.paraview.org/t/segmentation-fault-loguru-caught-a-signal-sigsegv/11148/22 "2023-01-22T23:29:15Z")

</div>

Don’t have the dataset in hand. But definitely recall such errors when developing a filter.

---

<div class="post-metadata">

### Author: ![jaswantp](https://discourse.paraview.org/user_avatar/discourse.paraview.org/jaswantp/32/11456_2.png) [@jaswantp](https://discourse.paraview.org/u/jaswantp)
#### Post date: [January 22, 2023, 11:30pm UTC](https://discourse.paraview.org/t/segmentation-fault-loguru-caught-a-signal-sigsegv/11148/23 "2023-01-22T23:30:37Z")

</div>

Will report when I see one!

---

<div class="post-metadata">

### Author: ![spyridon97](https://discourse.paraview.org/user_avatar/discourse.paraview.org/spyridon97/32/11569_2.png) [@spyridon97](https://discourse.paraview.org/u/spyridon97)
#### Post date: [January 22, 2023, 11:32pm UTC](https://discourse.paraview.org/t/segmentation-fault-loguru-caught-a-signal-sigsegv/11148/24 "2023-01-22T23:32:18Z")

</div>

Segfaults usually originate from out of memory accesses so, if you feed garbage to an algorithm that does not expect garbage then you are probably gonna have a problem. We could have an output consistency test at least memory access wise, but that’s gonna be an overhead for sure.

---

<div class="post-metadata">

### Author: ![jaswantp](https://discourse.paraview.org/user_avatar/discourse.paraview.org/jaswantp/32/11456_2.png) [@jaswantp](https://discourse.paraview.org/u/jaswantp)
#### Post date: [January 22, 2023, 11:34pm UTC](https://discourse.paraview.org/t/segmentation-fault-loguru-caught-a-signal-sigsegv/11148/25 "2023-01-22T23:34:59Z")

</div>

Yep, in the reported stack trace, the access violation originates from `vtkGeometryRepresentationWithFaces`. Those sanity checks you suggested would definitely help in both situations (readers and filters)

[Previous page](https://discourse.paraview.org/t/segmentation-fault-loguru-caught-a-signal-sigsegv/11148.md?page=1)
