&, bool) + 896
39 0x10951599f QCoreApplication::notifyInternal2(QObject*, QEvent*) + 159
38 0x10885f89d QApplication::notify(QObject*, QEvent*) + 7165
37 0x10885cb02 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 306
36 0x109ff6e1e QVTKOpenGLNativeWidget::event(QEvent*) + 30
35 0x109ffae52 QVTKRenderWindowAdapter::handleEvent(QEvent*) + 50
34 0x109ff57f3 QVTKInteractorAdapter::ProcessEvent(QEvent*, vtkRenderWindowInteractor*) + 3939
33 0x10e7ecdf5 vtkSubjectHelper::InvokeEvent(unsigned long, void*, vtkObject*) + 981
32 0x10e61b1e1 vtkCallbackCommand::Execute(vtkObject*, unsigned long, void*) + 33
31 0x10ac656c3 vtkPVInteractorStyle::OnMouseMove() + 147
30 0x10ac74c76 vtkPVTrackballRotate::OnMouseMove(int, int, vtkRenderer*, vtkRenderWindowInteractor*) + 998
29 0x10e7ecdf5 vtkSubjectHelper::InvokeEvent(unsigned long, void*, vtkObject*) + 981
28 0x10a17121b vtkSMViewProxyInteractorHelper::Render() + 331
27 0x10a16e1ff vtkSMViewProxy::InteractiveRender() + 191
26 0x10a66c017 vtkPVSessionBase::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 55
25 0x10a66e9c5 vtkPVSessionCore::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 85
24 0x10a66ec94 vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool) + 276
23 0x10bcce33d vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) + 61
22 0x10bcce610 vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) + 688
21 0x10bccf0aa vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) + 346
20 0x10bcd0496 vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) + 374
19 0x10f9d86b3 vtkPVRenderViewCommand(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*) + 2019
18 0x10a2d120c vtkPVRenderView::InteractiveRender() + 188
17 0x10a2d1c1e vtkPVRenderView::Render(bool, bool) + 2526
16 0x10c8c408e vtkGenericOpenGLRenderWindow::Render() + 62
15 0x10c9217de vtkOpenGLRenderWindow::Render() + 14
14 0x10d2ccd9c vtkRenderWindow::Render() + 332
13 0x10d2ccefc vtkRenderWindow::DoStereoRender() + 172
12 0x10d2db5a9 vtkRendererCollection::Render() + 137
11 0x10d2d5142 vtkRenderer::Render() + 1122
10 0x10d2d5706 vtkRenderer::AllocateTime() + 294
9 0x10d27078a vtkFrustumCoverageCuller::Cull(vtkRenderer*, vtkProp**, int&, int&) + 282
8 0x10ac67fdf vtkPVLODActor::GetBounds() + 63
7 0x10d2c06f9 vtkPolyDataMapper::GetBounds() + 153
6 0x10c8ab2f9 vtkCompositePolyDataMapper2::ComputeBounds() + 153
5 0x10d26213d vtkCompositeDataDisplayAttributes::ComputeVisibleBounds(vtkCompositeDataDisplayAttributes*, vtkDataObject*, double*) + 77
4 0x10d262352 vtkCompositeDataDisplayAttributes::ComputeVisibleBoundsInternal(vtkCompositeDataDisplayAttributes*, vtkDataObject*, vtkBoundingBox*, bool) + 434
3 0x10d2623af vtkCompositeDataDisplayAttributes::ComputeVisibleBoundsInternal(vtkCompositeDataDisplayAttributes*, vtkDataObject*, vtkBoundingBox*, bool) + 527
2 0x10dfdf076 vtkDataSet::GetBounds(double*) + 22
1 0x10e14a5ff vtkPolyData::ComputeBounds() + 367
0 0x7fff6dfe881f unw_resume + 10
( 68.128s) [paraview] :0 FATL| Signal: SIGSEGV
Segmentation fault: 11
```
---
### Author:  [@MBG](https://discourse.paraview.org/u/MBG)
#### Post date: [January 6, 2020, 5:22am UTC](https://discourse.paraview.org/t/macos-paraview-5-7-crashes-on-python-plugin-data-sources/3263/2 "2020-01-06T05:22:31Z")
There is no difference with added “RequestInformation()”. Also this release (and previous builds) crashes on internal XYZ reader and many other operations. ParaView 5.6.2 is much more stable but the plugins doesn’t work on it (and I couldn’t find any way to adopt the plugin to previous ParaView builds).
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [January 6, 2020, 9:33am UTC](https://discourse.paraview.org/t/macos-paraview-5-7-crashes-on-python-plugin-data-sources/3263/3 "2020-01-06T09:33:12Z")
I was not able to reproduce your crash. Please provide consistent steps to reproduce.
---
### Author:  [@MBG](https://discourse.paraview.org/u/MBG)
#### Post date: [January 6, 2020, 10:13am UTC](https://discourse.paraview.org/t/macos-paraview-5-7-crashes-on-python-plugin-data-sources/3263/4 "2020-01-06T10:13:45Z")
For example, this smalt text files crashes ParaView 5.7 & 5.6.2 when we try to open the file by internal XYZ reader:
[tesdata.xyz](https://discourse.paraview.org/uploads/short-url/efxo27FZTOvaMzajk7ba9GvOiBW.xyz) (12.1 KB)
The file is correct and we can process it by GDAL:
```
gdal_translate tesdata.xyz tesdata.tif
gdalinfo -stats tesdata.tif
Driver: GTiff/GeoTIFF
Files: tesdata.tif
Size is 21, 21
...
Band 1 Block=21x21 Type=Float32, ColorInterp=Gray
Minimum=0.065, Maximum=0.340, Mean=0.232, StdDev=0.073
Metadata:
STATISTICS_MAXIMUM=0.34000000357628
STATISTICS_MEAN=0.23193832301026
STATISTICS_MINIMUM=0.065399996936321
STATISTICS_STDDEV=0.072909508808815
STATISTICS_VALID_PERCENT=100
```
Also ParaView 5.7 crashes on every SEG-Y and LAS file too.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [January 6, 2020, 10:25am UTC](https://discourse.paraview.org/t/macos-paraview-5-7-crashes-on-python-plugin-data-sources/3263/5 "2020-01-06T10:25:51Z")
Your xyz file looks more like a .csv file. the xyz reader is a molecule reader :
> **[XYZ file format](https://en.wikipedia.org/wiki/XYZ_file_format)**
>
> The XYZ file format is a chemical file format. There is no formal standard and several variations exist, but a typical XYZ format specifies the molecule geometry by giving the number of atoms with Cartesian coordinates that will be read on the first line, a comment on the second, and the lines of atomic coordinates in the following lines. The file format is used in computational chemistry programs for importing and exporting geometries. The units are generally in ångströms. Some variations i Th...
Are you expecting a molecule or a geometry here ?
Here is a few working SEG-Y and LAS file for you to test with :
[pt000025\_v13.las](https://discourse.paraview.org/uploads/short-url/hBohuUIHxQ62TcjpAkTegRgDiE3.las) (699.8 KB)
[lineA.sgy](https://discourse.paraview.org/uploads/short-url/2av8J7bOYS5WsM7veTRV8LiTJxo.sgy) (1.6 MB)
---
### Author:  [@MBG](https://discourse.paraview.org/u/MBG)
#### Post date: [January 6, 2020, 10:52am UTC](https://discourse.paraview.org/t/macos-paraview-5-7-crashes-on-python-plugin-data-sources/3263/6 "2020-01-06T10:52:38Z")
Ah, ok, got it about the XYZ format. One suggestion: maybe some error message will be better than unexpected application crash?
Here is sampe LAS file which crashes ParaView 5.6.2 and 5.7:
[1050383876.las](https://discourse.paraview.org/uploads/short-url/ftmTI13aJBcdJlaTOMlHBfb94Wp.las) (1.5 MB)
Also, I could privately share a set of SEG-Y files which works fine in ParaView 5.6.2 but not in ParaView 5.7.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [January 6, 2020, 10:57am UTC](https://discourse.paraview.org/t/macos-paraview-5-7-crashes-on-python-plugin-data-sources/3263/7 "2020-01-06T10:57:26Z")
Indeed, a warning would be better, feel free to open an issue here [[1]](https://gitlab.kitware.com/paraview/paraview/issues).
Indeed, you .las file fails, feel free to open an issue here [[1]](https://gitlab.kitware.com/paraview/paraview/issues).
Please share you segy failing file in a private message.
---
### Author:  [@MBG](https://discourse.paraview.org/u/MBG)
#### Post date: [January 6, 2020, 12:33pm UTC](https://discourse.paraview.org/t/macos-paraview-5-7-crashes-on-python-plugin-data-sources/3263/8 "2020-01-06T12:33:04Z")
Ok, the issues opened. See the private issue:
[https://gitlab.kitware.com/paraview/paraview/issues/19559](https://gitlab.kitware.com/paraview/paraview/issues/19559)
Sorry, I can’t send the private message here.