Segment Violation

[sixburg]

What is the meaning and solution to this?  I've never before seen this on a Windows platform.  This is Mac El Capitan.  Latest PI release.  Occurred during simple ImageIntegration (WSC).


Critical signal caught (11): Segmentation violation


PixInsight 01.08.04.1195 - Critical Signal Backtrace
Signal : 11
Module : 0   PixInsight                          0x0000000106063df6 curl_slist_free_all + 1710659
========================================================================================================================
28: 1   libsystem_platform.dylib            0x00007fff88ae652a _sigtramp + 26
27: 2                                    0x00007ff907530f60 0x0 + 140707546468192
26: 3   PixInsight                          0x0000000105dd5040 start + 15021056
25: 4   QtCore                              0x0000000109f843e9 _ZN11QMetaObject8activateEP7QObjectiiPPv + 2953
24: 5   QtWidgets                           0x0000000108f73a70 _ZN7QAction8activateENS_11ActionEventE + 288
23: 6   QtCore                              0x0000000109f843e9 _ZN11QMetaObject8activateEP7QObjectiiPPv + 2953
22: 7   QtCore                              0x0000000109f7d0d3 _ZN7QObject5eventEP6QEvent + 755
21: 8   QtWidgets                           0x0000000108f7c953 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent + 307
20: 9   QtWidgets                           0x0000000108f7fc46 _ZN12QApplication6notifyEP7QObjectP6QEvent + 8022
19: 10  PixInsight                          0x00000001050b70c6 start + 1266822
18: 11  QtCore                              0x0000000109f548ec _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData + 956
17: 12  libqcocoa.dylib                     0x000000010e9c5fee qt_plugin_instance + 108366
16: 13  libqcocoa.dylib                     0x000000010e9c6861 qt_plugin_instance + 110529
15: 14  CoreFoundation                      0x00007fff84ad4621 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
14: 15  CoreFoundation                      0x00007fff84ab3e1c __CFRunLoopDoSources0 + 556
13: 16  CoreFoundation                      0x00007fff84ab333f __CFRunLoopRun + 927
12: 17  CoreFoundation                      0x00007fff84ab2d38 CFRunLoopRunSpecific + 296
11: 18  HIToolbox                           0x00007fff8cacdd55 RunCurrentEventLoopInMode + 235
10: 19  HIToolbox                           0x00007fff8cacda97 ReceiveNextEventCommon + 184
9: 20  HIToolbox                           0x00007fff8cacd9cf _BlockUntilNextEventMatchingListInModeWithFilter + 71
8: 21  AppKit                              0x00007fff93b1bf3a _DPSNextEvent + 1067
7: 22  AppKit                              0x00007fff93b1b369 -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454
6: 23  AppKit                              0x00007fff93b0fecc -[NSApplication run] + 682
5: 24  libqcocoa.dylib                     0x000000010e9c57ba qt_plugin_instance + 106266
4: 25  QtCore                              0x0000000109f5137c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE + 412
3: 26  QtCore                              0x0000000109f541ca _ZN16QCoreApplication4execEv + 346
2: 27  PixInsight                          0x00000001050cb5b3 start + 1350003
1: 28  PixInsight                          0x0000000104f81c74 start + 52

[sixburg]

Update on repeatability...

Window | Tile Windows will cause this to happen...sometimes.

[Juan Conejero]

This is a Qt 5 bug on OS X. It happens sometimes after WINDOW > Cascade Windows and WINDOW > Tile Windows, and is not reproducible following a known pattern, AFAIK.

However, the segfault does not cause the PixInsight Core application to exit, so you can continue working normally. This is what happens on all of our testing OS X machines.