Exiting BPP on Mojave 10.14.6 with PI 1.8.8-5

[grahamfletcher]

I get the following error(s) in process console window when exiting the BPP - any suggestions?:

<* failed *>

*** PCL Unix Signal Handler: Critical signal caught (11): Segmentation violation

PixInsight 1.8.8-5 - Critical Signal Backtrace
Received signal 11 (SIGSEGV)
Module: 0 PixInsight 0x000000010ce6b9fe InitializePixInsightModule + 1849342
================================================================================
36: 1 libsystem_platform.dylib 0x00007fff7a037b5d _sigtramp + 29
35: 2 QtGui 0x000000011509d126 _ZN11QAccessible24queryAccessibleInterfaceEP7QObject + 1014
34: 3 PixInsight 0x000000010cab68ea PixInsight + 13023466
33: 4 PixInsight 0x000000010cbded22 PixInsight + 14236962
32: 5 QtWidgets 0x0000000114b09702 _ZN7QWidget5eventEP6QEvent + 418
31: 6 QtWidgets 0x0000000114aced60 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent + 272
30: 7 QtWidgets 0x0000000114ad1cc6 _ZN12QApplication6notifyEP7QObjectP6QEvent + 7670
29: 8 PixInsight 0x000000010bf82be4 PixInsight + 1276900
28: 9 QtCore 0x0000000115a00bd4 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent + 212
27: 10 QtWidgets 0x0000000114acf687 _ZN19QApplicationPrivate14sendMouseEventEP7QWidgetP11QMouseEventS1_S1_PS1_R8QPointerIS0_Ebb + 903
26: 11 QtWidgets 0x0000000114b28a0f _ZN14QDesktopWidget11qt_metacallEN11QMetaObject4CallEiPPv + 9119
25: 12 QtWidgets 0x0000000114b2773a _ZN14QDesktopWidget11qt_metacallEN11QMetaObject4CallEiPPv + 4298
24: 13 QtWidgets 0x0000000114aced60 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent + 272
23: 14 QtWidgets 0x0000000114ad0115 _ZN12QApplication6notifyEP7QObjectP6QEvent + 581
22: 15 PixInsight 0x000000010bf82be4 PixInsight + 1276900
21: 16 QtCore 0x0000000115a00bd4 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent + 212
20: 17 QtGui 0x00000001150c3083 _ZN22QGuiApplicationPrivate17processMouseEventEPN29QWindowSystemInterfacePrivate10MouseEventE + 4003
19: 18 QtGui 0x00000001150a9f9b _ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE + 219
18: 19 libqcocoa.dylib 0x000000011966b648 qt_plugin_instance + 185384
17: 20 CoreFoundation 0x00007fff4dedfe33 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
16: 21 CoreFoundation 0x00007fff4dedfdd9 __CFRunLoopDoSource0 + 108
15: 22 CoreFoundation 0x00007fff4dec379b __CFRunLoopDoSources0 + 195
14: 23 CoreFoundation 0x00007fff4dec2d65 __CFRunLoopRun + 1189
13: 24 CoreFoundation 0x00007fff4dec266e CFRunLoopRunSpecific + 455
12: 25 HIToolbox 0x00007fff4d1211ab RunCurrentEventLoopInMode + 292
11: 26 HIToolbox 0x00007fff4d120ded ReceiveNextEventCommon + 355
10: 27 HIToolbox 0x00007fff4d120c76 _BlockUntilNextEventMatchingListInModeWithFilter + 64
9: 28 AppKit 0x00007fff4b4b877d _DPSNextEvent + 1135
8: 29 AppKit 0x00007fff4b4b746b -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361(+1361)
7: 30 AppKit 0x00007fff4b4b1588 -[NSApplication run] + 699
6: 31 libqcocoa.dylib 0x000000011966a4a8 qt_plugin_instance + 180872
5: 32 QtCore 0x00000001159fc31f _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE + 431
4: 33 QtCore 0x0000000115a01222 _ZN16QCoreApplication4execEv + 130
3: 34 PixInsight 0x000000010bf9b1ec PixInsight + 1376748
2: 35 libdyld.dylib 0x00007fff79e4c3d5 start + 1
1: 36 ??? 0x0000000000000001 0x0 + 1
================================================================================

 

[grahamfletcher]

Also happens on my Macbook Pro with Catalina

 

[Juan Conejero]

We cannot reproduce this on any of our working and testing Mac machines. This has not been reported before AFAIK. Also note that the segmentation violation is not happening in PixInsight code, but in QtGui, which is part of the Qt library.

Can you please provide a repeatable pattern, or a data set where this problem can be reproduced?

On a side note (probably unrelated to the specific problem you are reporting), the BatchPreprocessing script (BPP) has been deprecated and is no longer supported. You should be using the WeightedBatchPreprocessing script (WBPP) instead.

 

[grahamfletcher]

OK -thanks for the update - wasn't aware of the change - will try WBPP and see what happens.