# SegyReader broken in 5.7, 5.8?

**URL:** https://discourse.paraview.org/t/segyreader-broken-in-5-7-5-8/4762
**Category:** Development
**Created:** [July 6, 2020, 5:36pm UTC](https://discourse.paraview.org/t/segyreader-broken-in-5-7-5-8/4762 "2020-07-06T17:36:00Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![eroots](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/e/958977/32.png) [@eroots](https://discourse.paraview.org/u/eroots)
#### Post date: [July 6, 2020, 5:36pm UTC](https://discourse.paraview.org/t/segyreader-broken-in-5-7-5-8/4762/1 "2020-07-06T17:36:00Z")

</div>

I have been trying to import seismic data in the form of segy files into Paraview, and have run into a potential bug as of release 5.7.  
In 5.6, the SegyReader works perfectly and loads in the data as expected. However, in 5.7 and 5.8, the progress bar freezes at 50% and then fills my 25+ GB of RAM (file size is ~40 MB). As far as I’ve seen, the load never finishes and Paraview crashes after a while. At first I thought it was an issue with my files, but the fact that it loads fine in 5.6 suggests that something has changed between releases.

Can anyone confirm that this is the case, and not just an issue on my end?  
Thanks,

Eric

---

<div class="post-metadata">

### Author: ![wascott](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/w/8e8cbc/32.png) [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [July 6, 2020, 5:44pm UTC](https://discourse.paraview.org/t/segyreader-broken-in-5-7-5-8/4762/2 "2020-07-06T17:44:48Z")

</div>

Hi Eric,  
Welcome to the ParaView community!

Do you have a small-ish file that you could post that shows this behavior?

Alan

---

<div class="post-metadata">

### Author: ![eroots](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/e/958977/32.png) [@eroots](https://discourse.paraview.org/u/eroots)
#### Post date: [July 6, 2020, 6:16pm UTC](https://discourse.paraview.org/t/segyreader-broken-in-5-7-5-8/4762/3 "2020-07-06T18:16:59Z")

</div>

Here is a small test file that behaves as described:

[test.segy](https://discourse.paraview.org/uploads/short-url/8UHq9gMp6UAMkGurUs0xK9EYWN6.segy) (3.8 MB)

---

<div class="post-metadata">

### Author: ![wascott](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/w/8e8cbc/32.png) [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [July 6, 2020, 6:58pm UTC](https://discourse.paraview.org/t/segyreader-broken-in-5-7-5-8/4762/4 "2020-07-06T18:58:21Z")

</div>

Excellent. Mind writing up a bug in the bug tracker? It is found here: [https://gitlab.kitware.com/paraview/paraview/-/issues](https://gitlab.kitware.com/paraview/paraview/-/issues)

---

<div class="post-metadata">

### Author: ![eroots](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/e/958977/32.png) [@eroots](https://discourse.paraview.org/u/eroots)
#### Post date: [July 6, 2020, 8:57pm UTC](https://discourse.paraview.org/t/segyreader-broken-in-5-7-5-8/4762/5 "2020-07-06T20:57:49Z")

</div>

Done, thanks!

---

<div class="post-metadata">

### Author: ![utkarsh.ayachit](https://discourse.paraview.org/user_avatar/discourse.paraview.org/utkarsh.ayachit/32/39_2.png) [@utkarsh.ayachit](https://discourse.paraview.org/u/utkarsh.ayachit)
#### Post date: [July 7, 2020, 12:05pm UTC](https://discourse.paraview.org/t/segyreader-broken-in-5-7-5-8/4762/6 "2020-07-07T12:05:42Z")

</div>

Check **Force 2D** and the reader will read 2D datasets like this correctly. I don’t recall the details but these some information lacking in the format that doesn’t let the reader determine this on its own correctly.