MacOS ParaView 5.7 crashes on python plugin data sources

Development
1

I have a set of Python plugin data sources which works great separately. When two different data sources created MacOS ParaView crashes sometimes. Here is the plugin code: https://github.com/mobigroup/ParaView-plugins/blob/master/NCube/NCubeParaViewPlugin.py

/Applications/ParaView-5.7.0.app/Contents/MacOS/paraview

Loguru caught a signal: SIGSEGV
Stack trace:
64      0x7fff6ddc53d5 start + 1
63         0x1084d3f70 main + 592
62         0x109516092 QCoreApplication::exec() + 402
61         0x1095116f2 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 418
60         0x11be9444d qt_plugin_instance + 127181
59      0x7fff3f451588 -[NSApplication run] + 699
58      0x7fff3f45746b -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361
57      0x7fff3f45877d _DPSNextEvent + 1135
56      0x7fff410c0c76 _BlockUntilNextEventMatchingListInModeWithFilter + 64
55      0x7fff410c0ded ReceiveNextEventCommon + 355
54      0x7fff410c11ab RunCurrentEventLoopInMode + 292
53      0x7fff41e6266e CFRunLoopRunSpecific + 455
52      0x7fff41e62d65 __CFRunLoopRun + 1189
51      0x7fff41e6379b __CFRunLoopDoSources0 + 195
50      0x7fff41e7fdd9 __CFRunLoopDoSource0 + 108
49      0x7fff41e7fe33 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
48         0x11be95651 qt_plugin_instance + 131793
47         0x108e3336b QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 155
46         0x108e4c122 QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) + 2962
45         0x10951599f QCoreApplication::notifyInternal2(QObject*, QEvent*) + 159
44         0x10885de1f QApplication::notify(QObject*, QEvent*) + 383
43         0x10885cb02 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 306
42         0x1088b5779 QDesktopWidget::qt_metacall(QMetaObject::Call, int, void**) + 4649
41         0x1088b6b1c QDesktopWidget::qt_metacall(QMetaObject::Call, int, void**) + 9676
40         0x10885d430 QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, 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
2

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).

3

I was not able to reproduce your crash. Please provide consistent steps to reproduce.

4

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 (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.

5

Your xyz file looks more like a .csv file. the xyz reader is a molecule reader :

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 (699.8 KB)
lineA.sgy (1.6 MB)

6

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 (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.

7

Indeed, a warning would be better, feel free to open an issue here [1].

Indeed, you .las file fails, feel free to open an issue here [1].

Please share you segy failing file in a private message.

8

Ok, the issues opened. See the private issue:
https://gitlab.kitware.com/paraview/paraview/issues/19559

Sorry, I can’t send the private message here.