Author Topic: PCL Unix Signal Handler: Critical signal caught (11): Segmentation violation  (Read 299 times)

Offline JoeTourist

  • Newcomer
  • Posts: 1
    • View Profile
    • Joe Carr
I opened a file created by PI, and this error resulted. Mac Pro (Late 2013) running macOS Catalina and the latest update of PI.

Reading 1 image(s):
/Volumes/Astro1Tb/Astrophoto processing/2018.02.11-NGC2170/Resultants_PI/registered/Luminance/Light_Luminance_240.000secs_-37.30C_NGC_217000017831_c_r.xisf
Loading image: w=4524 h=3624 n=1 Gray Float32
3 image properties
94 FITS keyword(s) extracted.
*** PCL Unix Signal Handler: Critical signal caught (11): Segmentation violation
PixInsight 1.8.7 - Critical Signal Backtrace
Received signal 11 (SIGSEGV)
Module: 0   PixInsight                          0x000000010f76db22 InitializePixInsightModule + 1838082
================================================================================
 46: 1   libsystem_platform.dylib            0x00007fff6b491b1d _sigtramp + 29
 45: 2   ???                                 0x00007ffee148ec3c 0x0 + 140732678073404
 44: 3   PixInsight                          0x000000010f532cb2 PixInsight + 14437554
 43: 4   QtWidgets                           0x00000001173f03d4 _ZN7QWidget5eventEP6QEvent + 1172
 42: 5   QtWidgets                           0x00000001173b458f _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent + 271
 41: 6   QtWidgets                           0x00000001173b59ac _ZN12QApplication6notifyEP7QObjectP6QEvent + 588
 40: 7   PixInsight                          0x000000010e8a2c84 PixInsight + 1264772
 39: 8   QtCore                              0x00000001182f0fc4 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent + 212
 38: 9   QtWidgets                           0x00000001173ef17d _ZN14QWidgetPrivate11show_helperEv + 413
 37: 10  QtWidgets                           0x00000001173efd80 _ZN14QWidgetPrivate10setVisibleEb + 816
 36: 11  PixInsight                          0x000000010f42caa1 PixInsight + 13363873
 35: 12  PixInsight                          0x000000010ea2493d PixInsight + 2844989
 34: 13  PixInsight                          0x000000010ea2dde2 PixInsight + 2883042
 33: 14  QtCore                              0x00000001182f128e _ZN23QCoreApplicationPrivate29sendThroughObjectEventFiltersEP7QObjectP6QEvent + 206
 32: 15  QtWidgets                           0x00000001173b457a _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent + 250
 31: 16  QtWidgets                           0x00000001173b59ac _ZN12QApplication6notifyEP7QObjectP6QEvent + 588
 30: 17  PixInsight                          0x000000010e8a2c84 PixInsight + 1264772
 29: 18  QtCore                              0x00000001182f0fc4 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent + 212
 28: 19  QtWidgets                           0x00000001173b406a _ZN19QApplicationPrivate18dispatchEnterLeaveEP7QWidgetS1_RK7QPointF + 1674
 27: 20  QtWidgets                           0x00000001173b4e81 _ZN19QApplicationPrivate14sendMouseEventEP7QWidgetP11QMouseEventS1_S1_PS1_R8QPointerIS0_Ebb + 833
 26: 21  QtWidgets                           0x000000011740f2cc _ZN14QDesktopWidget11qt_metacallEN11QMetaObject4CallEiPPv + 9132
 25: 22  QtWidgets                           0x000000011740dfeb _ZN14QDesktopWidget11qt_metacallEN11QMetaObject4CallEiPPv + 4299
 24: 23  QtWidgets                           0x00000001173b458f _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent + 271
 23: 24  QtWidgets                           0x00000001173b59ac _ZN12QApplication6notifyEP7QObjectP6QEvent + 588
 22: 25  PixInsight                          0x000000010e8a2c84 PixInsight + 1264772
 21: 26  QtCore                              0x00000001182f0fc4 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent + 212
 20: 27  QtGui                               0x00000001179a5ea9 _ZN22QGuiApplicationPrivate17processMouseEventEPN29QWindowSystemInterfacePrivate10MouseEventE + 3449
 19: 28  QtGui                               0x000000011798ca9b _ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE + 219
 18: 29  libqcocoa.dylib                     0x000000011bfb2580 qt_plugin_instance + 183808
 17: 30  libqcocoa.dylib                     0x000000011bfb2cf8 qt_plugin_instance + 185720
 16: 31  CoreFoundation                      0x00007fff33ef93d6 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
 15: 32  CoreFoundation                      0x00007fff33ef9375 __CFRunLoopDoSource0 + 103
 14: 33  CoreFoundation                      0x00007fff33edceb9 __CFRunLoopDoSources0 + 209
 13: 34  CoreFoundation                      0x00007fff33edc4af __CFRunLoopRun + 1282
 12: 35  CoreFoundation                      0x00007fff33edbd38 CFRunLoopRunSpecific + 503
 11: 36  HIToolbox                           0x00007fff32a58b2d RunCurrentEventLoopInMode + 292
 10: 37  HIToolbox                           0x00007fff32a58779 ReceiveNextEventCommon + 356
  9: 38  HIToolbox                           0x00007fff32a585f7 _BlockUntilNextEventMatchingListInModeWithFilter + 64
  8: 39  AppKit                              0x00007fff310eeac4 _DPSNextEvent + 990
  7: 40  AppKit                              0x00007fff310ed834 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352(+1352)
  6: 41  AppKit                              0x00007fff310e7fd4 -[NSApplication run] + 658
  5: 42  libqcocoa.dylib                     0x000000011bfb1a85 qt_plugin_instance + 180997
  4: 43  QtCore                              0x00000001182ec5cf _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE + 431
  3: 44  QtCore                              0x00000001182f1632 _ZN16QCoreApplication4execEv + 130
  2: 45  PixInsight                          0x000000010e8b9e3b PixInsight + 1359419
  1: 46  libdyld.dylib                       0x00007fff6b28c405 start + 1
================================================================================

Online Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 6838
    • View Profile
    • http://pixinsight.com/
Hi Joe,

Thanks for the report. We cannot reproduce this problem, and nothing similar has been reported so far for versions 1.8.6 and 1.8.7. Is this a repeatable issue for you?

The segmentation violation occurs in the InitializePixInsightModule routine, which is part of the module installation process in the PixInsight core application. Are you using a nonstandard or third-party module?
Juan Conejero
PixInsight Development Team
http://pixinsight.com/

Offline jbinpg

  • Newcomer
  • Posts: 14
    • View Profile
Unfortunately, I find myself in the same boat. After applying the latest updates, the ImageIntegration module is crashing as follows:

Integration of 48 images:
Pixel combination .................. average
Output normalization ............... additive + scaling
Weighting mode ..................... noise evaluation
Scale estimator .................... iterative k-sigma / BWMV
Pixel rejection .................... linear fit clipping
Rejection normalization ............ scale + zero offset
Rejection clippings ................ low=yes high=yes
Rejection parameters ............... lfit_low=5.000 lfit_high=4.000

* Available physical memory: 27.214 GiB
* Allocated pixel buffer: 4932 rows, 6.505 GiB
* Using 3466 concurrent pixel stack(s), 13.904 GiB


* Integrating channel 1 of 3:
*** PCL Unix Signal Handler: Critical signal caught (11): Segmentation violation
PixInsight 1.8.7 - Critical Signal Backtrace
Received signal 11 (SIGSEGV)
Module: /opt/PixInsight/bin/PixInsight(+0x16d717c) [0x562d4cd3a17c]
================================================================================
 41: /lib/x86_64-linux-gnu/libpthread.so.0(+0x15540) [0x7f003cb6d540]
 40: /opt/PixInsight/bin/ImageIntegration-pxm.so(+0x192171) [0x7eff4e362171]
 39: /opt/PixInsight/bin/ImageIntegration-pxm.so(+0x2a3a91) [0x7eff4e473a91]
 38: pi::MetaProcess::ExecuteGlobal(void*) const(+0x58 [0x562d4c8a3868])
 37: pi::ProcessInstance::ExecuteGlobal()(+0xa7 [0x562d4c8d02c7])
 36: pi::APIGlobalContext::LaunchProcessInstance(void const*, void const*, int, unsigned int)(+0xf9 [0x562d4bdc7259])
 35: /opt/PixInsight/bin/ImageIntegration-pxm.so(+0x3420af) [0x7eff4e5120af]
 34: pi::ProcessInterface::ApplyGlobal()(+0x99 [0x562d4c8fb019])
 33: /opt/PixInsight/bin/PixInsight(+0x14aad45) [0x562d4cb0dd45]
 32: QMetaObject::activate(QObject*, int, int, void**)(+0x7b8 [0x7f003394c1c8])
 31: QAbstractButton::clicked(bool)(+0x42 [0x7f00347ce4d2])
 30: /opt/PixInsight/bin/lib/libQt5Widgets.so.5(+0x26e6ea) [0x7f00347ce6ea]
 29: /opt/PixInsight/bin/lib/libQt5Widgets.so.5(+0x26fa8f) [0x7f00347cfa8f]
 28: QAbstractButton::mouseReleaseEvent(QMouseEvent*)(+0xe5 [0x7f00347cfc55])
 27: QToolButton::mouseReleaseEvent(QMouseEvent*)(+0xa [0x7f00348bea3a])
 26: QWidget::event(QEvent*)(+0x246 [0x7f003471e936])
 25: QToolButton::event(QEvent*)(+0x34 [0x7f00348beae4])
 24: QApplicationPrivate::notify_helper(QObject*, QEvent*)(+0x82 [0x7f00346dcd42])
 23: QApplication::notify(QObject*, QEvent*)(+0x583 [0x7f00346e64f3])
 22: pi::PixInsightApplication::notify(QObject*, QEvent*)(+0x1f [0x562d4be85f7f])
 21: QCoreApplication::notifyInternal2(QObject*, QEvent*)(+0x182 [0x7f00339215e2])
 20: QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer, bool, bool)(+0x1b3 [0x7f00346e5603])
 19: /opt/PixInsight/bin/lib/libQt5Widgets.so.5(+0x1da209) [0x7f003473a209]
 18: /opt/PixInsight/bin/lib/libQt5Widgets.so.5(+0x1dd094) [0x7f003473d094]
 17: QApplicationPrivate::notify_helper(QObject*, QEvent*)(+0x82 [0x7f00346dcd42])
 16: QApplication::notify(QObject*, QEvent*)(+0x330 [0x7f00346e62a0])
 15: pi::PixInsightApplication::notify(QObject*, QEvent*)(+0x1f [0x562d4be85f7f])
 14: QCoreApplication::notifyInternal2(QObject*, QEvent*)(+0x182 [0x7f00339215e2])
 13: QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)(+0x6c3 [0x7f0034020713])
 12: QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)(+0x24b [0x7f0034021f6b])
 11: QWindowSystemInterface::sendWindowSystemEvents(QFlags)(+0xbb [0x7f0033ffcbab])
 10: /opt/PixInsight/bin/lib/libQt5XcbQpa.so.5(+0x6de7a) [0x7f003027de7a]
  9: /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x27d) [0x7f003172184d](+0x27d [0x7f003172184d])
  8: /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x51ad0) [0x7f0031721ad0]
  7: /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x33) [0x7f0031721b73](+0x33 [0x7f0031721b73])
  6: QEventDispatcherGlib::processEvents(QFlags)(+0x61 [0x7f00339775c1])
  5: QEventLoop::exec(QFlags)(+0x12b [0x7f003392026b])
  4: QCoreApplication::exec()(+0x92 [0x7f0033927d12])
  3: /opt/PixInsight/bin/PixInsight(main+0x36ea) [0x562d4bced6ca](+0x36ea [0x562d4bced6ca])
  2: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7f00327971e3](+0xf3 [0x7f00327971e3])
  1: /opt/PixInsight/bin/PixInsight(_start+0x2a) [0x562d4bd3341a](+0x2a [0x562d4bd3341a])
================================================================================
<* failed *>

Ubuntu 19.10, kernel 5.3.0-19-generic. I successfully completed one integration after applying the update but any subsequent attempts fail. Changing any of the integration parameters including disabling the file cache does not alleviate the crash. I have cold booted the computer and restarted PI to no effect.

Jack

Offline jbinpg

  • Newcomer
  • Posts: 14
    • View Profile
OK, it took a while to figure this one out but there is nothing wrong with PixInsight 1.8.7.

It turns out that I had a corrupted file that ImageIntegration was choking on. I went through the system logs and found that there was a file cleaning routine running on the same drive that houses my data files when I was working with PI. I then went back and took a closer look at the process log and found that, indeed, PI could not read the last file in the directory. So I deleted that file and returned all the integration settings to their defaults and wvwerything worked. The file must have been clobbered by the file cleaning routine so I disabled the routine permanently.

Sorry for the misdirection. Perhaps the PI team could find a way to make the integration fail more gracefully when encountering a bad file? I know this is done in the other modules but perhaps the integration module is more difficult to program in this way.

cheers,
Jack

 

Online Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 6838
    • View Profile
    • http://pixinsight.com/
Hi Jack,

A segmentation fault is a segmentation fault; there is no more graceful way to handle it. Unfortunately, 'bad file' is such a vague concept that everything is possible. We cannot protect our code against all possible ill-conditioned situations generated by misbehaving third-party software that tampers with data while we are processing it. We can only try to guarantee that things work reasonably well under normal conditions, and that is difficult enough to achieve :)
Juan Conejero
PixInsight Development Team
http://pixinsight.com/