›

Crashes every chance it gets

Robert Dalton
in PixInsight
Not sure if you can help me, I am running a 2020 Mac Intel with Sonoma and I cannot update to any version above 1.8.8.x of Pixinsight.  If I do a clean install or even wipe my computer and install MacOS new, not from my timemachine and install 1.8.9.x it gets the following error when trying to use the apply instance (little triangle bottom left) of any command, e.g. BlurExterminator or Curves or even pixelmath.

I don't believe that the developers are interested in addressing the issue, stating in the Pixinsight forum "cannot reproduce" and closing my tickets.

Do you have a solution or suggestion?

PixInsight 1.8.9-2 - Critical Signal Backtrace
Received signal 11 (SIGSEGV)
Module: 0   PixInsight                          0x000000010b76c82e InitializePixInsightModule + 2253710
================================================================================
 73: 1   libsystem_platform.dylib            0x00007ff81796d37d _sigtramp + 29
 72: 2   ???                                 0x98fc07fc77fbe7fa 0x0 + 11023694768822282234
 71: 3   PixInsight                          0x000000010b476fea PixInsight + 13840362
 70: 4   QtWidgets                           0x000000010e1b71a7 _ZN7QWidget5eventEP6QEvent + 1031
 69: 5   QtWidgets                           0x000000010e167ca1 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent + 241
 68: 6   QtWidgets                           0x000000010e168ad1 _ZN12QApplication6notifyEP7QObjectP6QEvent + 481
 67: 7   PixInsight                          0x000000010a872e74 PixInsight + 1240692
 66: 8   QtCore                              0x000000010e7f014c _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent + 172
 65: 9   QtWidgets                           0x000000010e1a9412 _ZN14QWidgetPrivate10drawWidgetEP12QPaintDeviceRK7QRegionRK6QPoint6QFlagsINS_14DrawWidgetFlagEEP8QPainterP21QWidgetRepaintManager + 3602
 64: 10  QtWidgets                           0x000000010e1c8790 _ZN21QWidgetRepaintManager13paintAndFlushEv + 5088
 63: 11  QtWidgets                           0x000000010e1c8a6e _ZN21QWidgetRepaintManager4syncEv + 254
 62: 12  QtWidgets                           0x000000010e1b73cb _ZN7QWidget5eventEP6QEvent + 1579
 61: 13  QtWidgets                           0x000000010e167ca1 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent + 241
 60: 14  QtWidgets                           0x000000010e168ad1 _ZN12QApplication6notifyEP7QObjectP6QEvent + 481
 59: 15  PixInsight                          0x000000010a872e74 PixInsight + 1240692
 58: 16  QtCore                              0x000000010e7f014c _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent + 172
 57: 17  QtWidgets                           0x000000010e1c4d23 _ZN21QWidgetRepaintManager17sendUpdateRequestEP7QWidgetNS_10UpdateTimeE + 627
 56: 18  QtWidgets                           0x000000010e1c4a91 _ZN21QWidgetRepaintManager9markDirtyI5QRectEEvRKT_P7QWidgetNS_10UpdateTimeENS_11BufferStateE + 2097
 55: 19  QtWidgets                           0x000000010e1b9ef7 _ZN7QWidget7repaintEv + 167
 54: 20  PixInsight                          0x000000010b48b8d3 PixInsight + 13924563
 53: 21  QtCore                              0x000000010e837db5 _ZN7QObject5eventEP6QEvent + 581
 52: 22  QtWidgets                           0x000000010e1b7ba4 _ZN7QWidget5eventEP6QEvent + 3588
 51: 23  QtWidgets                           0x000000010e167ca1 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent + 241
 50: 24  QtWidgets                           0x000000010e168ad1 _ZN12QApplication6notifyEP7QObjectP6QEvent + 481
 49: 25  PixInsight                          0x000000010a872e74 PixInsight + 1240692

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

Comments

  • BlockHeadBlockHead
    Segmentation violations or faults are generally memory problems. They could be caused by a program doing bad things (trying to write in memory to a place out of bounds). However, it can also be a real hardware memory issue. Since there are not hundreds of people complaining about this particular error...
    it would seem to be likely an issue on your end.

    You need to install PI on another machine and convince yourself this isn't a software issue.

    -the Blockhead
  • Robert Dalton
    Thanks,

    I only have the one intel machine.  I could put pixinsight on my MacBook Air with an apple silicone chip, but then I would be forced to use a 12 inch monitor.  Not much of an option.  I have been complaining about this error since the release of 1.8.9.  Odd that with 256 gigs of Ram and 10TB of hard drive space and the fact that version 1.8.8 works flawlessly I guess I just won't be doing updates and paid for a software that has reached its end of life.

    oh well....
  • BlockHeadBlockHead
    There was a thread about instruction sets that deal with (older) hardware.
    I do not know if this is related. 
    -the Blockhead
Sign In or Register to comment.