Author Topic: Unknown exception  (Read 374 times)

Offline thutchison

  • Newcomer
  • Posts: 10
    • View Profile
Unknown exception
« on: 2019 August 04 14:08:03 »
I have been getting an unknown exception at seemingly random and inconsistent times while using PI lately.  I have version 1.08.06.1475 Ripley.  Here is the exception.

Thank you in advance for your assistance.
Tim.

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

PixInsight 01.08.06.1475 - Critical Signal Backtrace

Received signal 11 (SIGSEGV)

Module: 0   PixInsight                          0x00000001064bf382 InitializePixInsightModule + 1868482

================================================================================

 40: 1   libsystem_platform.dylib            0x00007fff75651b5d _sigtramp + 29

 39: 2   PixInsight                          0x000000010693a62b _cmsTransformPluginChunk + 214955

 38: 3   QtWidgets                           0x00000001075fcfe5 _ZN14QWidgetPrivate11show_helperEv + 421

 37: 4   QtWidgets                           0x00000001075fdc00 _ZN14QWidgetPrivate10setVisibleEb + 832

 36: 5   PixInsight                          0x00000001058b79db PixInsight + 4405723

 35: 6   PixInsight                          0x00000001058ba475 PixInsight + 4416629

 34: 7   QtWidgets                           0x00000001075fdfac _ZN7QWidget5eventEP6QEvent + 492

 33: 8   QtWidgets                           0x00000001075c250f _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent + 271

 32: 9   QtWidgets                           0x00000001075c53ad _ZN12QApplication6notifyEP7QObjectP6QEvent + 7373

 31: 10  PixInsight                          0x00000001055c6514 PixInsight + 1320212

 30: 11  QtCore                              0x00000001084e1544 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent + 212

 29: 12  QtWidgets                           0x00000001075c2e44 _ZN19QApplicationPrivate14sendMouseEventEP7QWidgetP11QMouseEventS1_S1_PS1_R8QPointerIS0_Ebb + 900

 28: 13  QtWidgets                           0x000000010761d0fc _ZN14QDesktopWidget11qt_metacallEN11QMetaObject4CallEiPPv + 9132

 27: 14  QtWidgets                           0x000000010761be1b _ZN14QDesktopWidget11qt_metacallEN11QMetaObject4CallEiPPv + 4299

 26: 15  QtWidgets                           0x00000001075c250f _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent + 271

 25: 16  QtWidgets                           0x00000001075c392c _ZN12QApplication6notifyEP7QObjectP6QEvent + 588

 24: 17  PixInsight                          0x00000001055c6514 PixInsight + 1320212

 23: 18  QtCore                              0x00000001084e1544 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent + 212

 22: 19  QtGui                               0x0000000107bb25f6 _ZN22QGuiApplicationPrivate17processMouseEventEPN29QWindowSystemInterfacePrivate10MouseEventE + 3462

 21: 20  QtGui                               0x0000000107bb2975 _ZN22QGuiApplicationPrivate17processMouseEventEPN29QWindowSystemInterfacePrivate10MouseEventE + 4357

 20: 21  QtGui                               0x0000000107bb63e9 _ZN22QGuiApplicationPrivate18processTabletEventEPN29QWindowSystemInterfacePrivate11TabletEventE + 1689

 19: 22  QtGui                               0x0000000107b9992b _ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE + 219

 18: 23  libqcocoa.dylib                     0x000000010c192b30 qt_plugin_instance + 178048

 17: 24  libqcocoa.dylib                     0x000000010c1932a0 qt_plugin_instance + 179952

 16: 25  CoreFoundation                      0x00007fff494bedbb __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17

 15: 26  CoreFoundation                      0x00007fff494bed61 __CFRunLoopDoSource0 + 108

 14: 27  CoreFoundation                      0x00007fff494a2c6b __CFRunLoopDoSources0 + 195

 13: 28  CoreFoundation                      0x00007fff494a2233 __CFRunLoopRun + 1196

 12: 29  CoreFoundation                      0x00007fff494a1b35 CFRunLoopRunSpecific + 459

 11: 30  HIToolbox                           0x00007fff4878096b RunCurrentEventLoopInMode + 292

 10: 31  HIToolbox                           0x00007fff487805ad ReceiveNextEventCommon + 355

  9: 32  HIToolbox                           0x00007fff48780436 _BlockUntilNextEventMatchingListInModeWithFilter + 64

  8: 33  AppKit                              0x00007fff46b1a987 _DPSNextEvent + 965

  7: 34  AppKit                              0x00007fff46b1971f -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361(+1361)

  6: 35  AppKit                              0x00007fff46b1383c -[NSApplication run] + 699

  5: 36  libqcocoa.dylib                     0x000000010c192216 qt_plugin_instance + 175718

  4: 37  QtCore                              0x00000001084dcbff _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE + 431

  3: 38  QtCore                              0x00000001084e1bb2 _ZN16QCoreApplication4execEv + 130

  2: 39  PixInsight                          0x00000001055de7da PixInsight + 1419226

  1: 40  libdyld.dylib                       0x00007fff754663d5 start + 1

================================================================================

Online Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 6715
    • View Profile
    • http://pixinsight.com/
Re: Unknown exception
« Reply #1 on: 2019 August 09 04:03:21 »
Hi Tim,

From the backtrace, it seems the crash happens within LittleCMS code (the color management engine used by the PixInsight core application). This problem cannot be reproduced on any of our working macOS machines. Which version of macOS are you using? Does this happen with some particular images? If yes, can you upload some of them?
Juan Conejero
PixInsight Development Team
http://pixinsight.com/

Offline thutchison

  • Newcomer
  • Posts: 10
    • View Profile
Re: Unknown exception
« Reply #2 on: 2019 August 24 07:01:10 »
I am using Mojave version 10.14.6.  I will send an image the next time I see the exception.

Please forgive the delay in responding.  Life getting in the way of my hobby! :)

Offline thutchison

  • Newcomer
  • Posts: 10
    • View Profile
Re: Unknown exception
« Reply #3 on: 2019 September 08 11:43:31 »
I have had this issue recurring quite frequently.  I have a project file with all images from my most recent crash. The file is FAR too big to attach.  How would you like for me to get that to you?

Thank you for the help.
Tim.

Offline tmlewis48

  • Newcomer
  • Posts: 1
    • View Profile
Re: Unknown exception
« Reply #4 on: 2019 September 09 14:54:39 »
If you recently installed the windows 10 update, you might check Windows security to make sure that PI hasn't been blocked.  I hadn't processed anything for about 6  weeks and was surprized to be getting win 32 messages and being unable to save files.  I went to Windows security and unblocked several PI modules--everything now OK

Offline thutchison

  • Newcomer
  • Posts: 10
    • View Profile
Re: Unknown exception
« Reply #5 on: 2019 September 09 22:48:04 »
Thanks for the reply but I'm using a mac.

Online Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 6715
    • View Profile
    • http://pixinsight.com/
Re: Unknown exception
« Reply #6 on: 2019 September 10 01:58:10 »
Tim,

You can use a cloud storage service such as Dropbox to upload big files. As I said before, the backtrace shows that the problem originates in LittleCMS code (to which the _cmsTransformPluginChunk routine belongs), so it seems related to color management. Additional questions:

- Do you get the '_cmsTransformPluginChunk' name listed at the top of all backtraces? Or, for that matter, any name beginning with '_cms'?

- Have you calibrated your monitor with a third-party utility?

- Or, are you using a custom ICC profile for your monitor, different from the profile assigned automatically by macOS?

ICC profiles are complex and can lead to crash if they are not valid structurally or numerically. A defective ICC profile can be the cause of these problems.
Juan Conejero
PixInsight Development Team
http://pixinsight.com/

Offline thutchison

  • Newcomer
  • Posts: 10
    • View Profile
Re: Unknown exception
« Reply #7 on: 2019 September 13 09:50:48 »
Juan:
I greatly appreciate your reply.

I was using a color calibration profile generated by a third party tool and thought you had hit on the issue.  I changed back to the ICC profile that came with the operating system and I'm still having the issue.  Here is the latest trace. I had a few images open at the time and was using the HistoryExplorer to look at their history.  I was using the drop down at the lower left to change images when this occurred, i.e. I had just selected an image from the drop down and the "Unknown Exception" dialog box popped up.

I appreciate your assistance very much.
Tim.

*** PCL Unix Signal Handler: Critical signal caught (11): Segmentation violation
PixInsight 01.08.06.1475 - Critical Signal Backtrace
Received signal 11 (SIGSEGV)
Module: 0   PixInsight                          0x000000010e4f9382 InitializePixInsightModule + 1868482
================================================================================
 41: 1   libsystem_platform.dylib            0x00007fff650d9b5d _sigtramp + 29
 40: 2   ???                                 0x00007ffee273f048 0x0 + 140732697669704
 39: 3   QtWidgets                           0x0000000116377fe5 _ZN14QWidgetPrivate11show_helperEv + 421
 38: 4   QtWidgets                           0x0000000116378c00 _ZN14QWidgetPrivate10setVisibleEb + 832
 37: 5   PixInsight                          0x000000010d8ef23d PixInsight + 4395581
 36: 6   PixInsight                          0x000000010d8ef4bf PixInsight + 4396223
 35: 7   QtWidgets                           0x0000000116378fac _ZN7QWidget5eventEP6QEvent + 492
 34: 8   QtWidgets                           0x0000000116441a23 _ZN9QComboBox5eventEP6QEvent + 371
 33: 9   QtWidgets                           0x000000011633d50f _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent + 271
 32: 10  QtWidgets                           0x00000001163403ad _ZN12QApplication6notifyEP7QObjectP6QEvent + 7373
 31: 11  PixInsight                          0x000000010d600514 PixInsight + 1320212
 30: 12  QtCore                              0x00000001171c0544 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent + 212
 29: 13  QtWidgets                           0x000000011633de44 _ZN19QApplicationPrivate14sendMouseEventEP7QWidgetP11QMouseEventS1_S1_PS1_R8QPointerIS0_Ebb + 900
 28: 14  QtWidgets                           0x00000001163980fc _ZN14QDesktopWidget11qt_metacallEN11QMetaObject4CallEiPPv + 9132
 27: 15  QtWidgets                           0x0000000116396e1b _ZN14QDesktopWidget11qt_metacallEN11QMetaObject4CallEiPPv + 4299
 26: 16  QtWidgets                           0x000000011633d50f _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent + 271
 25: 17  QtWidgets                           0x000000011633e92c _ZN12QApplication6notifyEP7QObjectP6QEvent + 588
 24: 18  PixInsight                          0x000000010d600514 PixInsight + 1320212
 23: 19  QtCore                              0x00000001171c0544 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent + 212
 22: 20  QtGui                               0x000000011692d5f6 _ZN22QGuiApplicationPrivate17processMouseEventEPN29QWindowSystemInterfacePrivate10MouseEventE + 3462
 21: 21  QtGui                               0x000000011692d975 _ZN22QGuiApplicationPrivate17processMouseEventEPN29QWindowSystemInterfacePrivate10MouseEventE + 4357
 20: 22  QtGui                               0x00000001169313e9 _ZN22QGuiApplicationPrivate18processTabletEventEPN29QWindowSystemInterfacePrivate11TabletEventE + 1689
 19: 23  QtGui                               0x000000011691492b _ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE + 219
 18: 24  libqcocoa.dylib                     0x000000011ad90b30 qt_plugin_instance + 178048
 17: 25  libqcocoa.dylib                     0x000000011ad912a0 qt_plugin_instance + 179952
 16: 26  CoreFoundation                      0x00007fff38f1f3bb __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
 15: 27  CoreFoundation                      0x00007fff38f1f361 __CFRunLoopDoSource0 + 108
 14: 28  CoreFoundation                      0x00007fff38f0326b __CFRunLoopDoSources0 + 195
 13: 29  CoreFoundation                      0x00007fff38f02833 __CFRunLoopRun + 1196
 12: 30  CoreFoundation                      0x00007fff38f02135 CFRunLoopRunSpecific + 459
 11: 31  HIToolbox                           0x00007fff381531ab RunCurrentEventLoopInMode + 292
 10: 32  HIToolbox                           0x00007fff38152ded ReceiveNextEventCommon + 355
  9: 33  HIToolbox                           0x00007fff38152c76 _BlockUntilNextEventMatchingListInModeWithFilter + 64
  8: 34  AppKit                              0x00007fff364eb79d _DPSNextEvent + 1135
  7: 35  AppKit                              0x00007fff364ea48b -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361(+1361)
  6: 36  AppKit                              0x00007fff364e45a8 -[NSApplication run] + 699
  5: 37  libqcocoa.dylib                     0x000000011ad90216 qt_plugin_instance + 175718
  4: 38  QtCore                              0x00000001171bbbff _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE + 431
  3: 39  QtCore                              0x00000001171c0bb2 _ZN16QCoreApplication4execEv + 130
  2: 40  PixInsight                          0x000000010d6187da PixInsight + 1419226
  1: 41  libdyld.dylib                       0x00007fff64eee3d5 start + 1
================================================================================

Online pfile

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 4309
    • View Profile
Re: Unknown exception
« Reply #8 on: 2019 September 13 10:21:01 »
what kind of machine is this? is it a laptop?

have you run Prime95 or memtest86+ on it to see if there's some generic problem with the computer?

rob

Offline thutchison

  • Newcomer
  • Posts: 10
    • View Profile
Re: Unknown exception
« Reply #9 on: 2019 September 13 11:25:03 »
Thank you for your reply.

The machine is a Mac Pro.  The error that we are seeing is a segmentation violation, which is a software exception, not a hardware error.  I can try to find those tests and run them, but I'm rather certain that is not the issue.  Can we verify this is necessary before I go down this road? 

Thank you.
Tim.

Online pfile

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 4309
    • View Profile
Re: Unknown exception
« Reply #10 on: 2019 September 13 11:52:33 »
well i hate to break it to you but software issues can be caused by hardware issues. if the cooling/thermal design is suspect (which it is on the latest macbooks, which is why i asked) then the processor can overheat and without going into too much detail, the high temperature can cause calculation errors which eventually show up as a segmentation violation, since a pointer or jump target address is computed improperly pointing outside the address space of the process in question.

anyway when you see segfaults in all kinds of different parts of the code its more likely to be a hardware problem than a software problem.

having said all this i would not necessarily expect a mac pro to have the same thermal issues as a macbook, though the "trash can" mac pro design is somewhat thermally constrained.

rob

Offline thutchison

  • Newcomer
  • Posts: 10
    • View Profile
Re: Unknown exception
« Reply #11 on: 2019 September 13 12:07:30 »
So what are you asking me to do to help troubleshoot this further?

Online pfile

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 4309
    • View Profile
Re: Unknown exception
« Reply #12 on: 2019 September 13 12:32:57 »
well i am saying although it may be a longshot, it is worth running other benchmarks that stress the machine to see what happens. if prime95 throws errors or memtest86+ throws errors then you can investigate possible hardware issues. i only say this because these kinds of segfaults on the mac version of PI are pretty unusual.

memtest86+ is kind of a pain though as without booting the machine directly into memtest86+, it can't test all of the computer's memory. making a bootable memtest86+ disc/USB for a mac is a little more involved than making one for a windows machine, but it can be done.

did these errors occur while the machine was doing StarAlignment or ImageIntegration or other CPU-intensive tasks? or while the machine was just sitting there?

do you have any kind of antivirus software installed? i think we've seen bad interactions in the past with mac AV stuff.

rob