Author Topic: PixInsight 1.8.6 critical signal violations in Process Console  (Read 363 times)

Offline jtalbot

  • PixInsight Enthusiast
  • **
  • Posts: 75
    • View Profile
    • http://www.starscapeimaging.com
Juan,
In the process console I'm seeing a lot of "red" Critical Signal violation messages and after that happens, Icons within PixInsight 1.8.6 start acting funny and sometime disappear.  No crashes  yet but something is up with the QT core. This is happening every time I run PixInsight after installing 1.8.6.   System is a IMAC 5K late 2015, Intel Core I7 4GHZ, 32 gb of Ram.  See attached.

Best,
Jon
Clear Skies

Jon

Offline Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 7089
    • View Profile
    • http://pixinsight.com/
Re: PixInsight 1.8.6 critical signal violations in Process Console
« Reply #1 on: 2019 January 11 11:09:54 »
Hi Jon,

Bug confirmed. This one has been *really* difficult to find, but I finally have managed to reproduce and understand it after a whole day of work. I am working to fix it right now.

This problem happens in the new version 1.8.6 of PixInsight on all platforms. It occurs when an image window attempts to generate a screen rendition from nonexistent image pixels, as a result of invalid screen coordinate calculations. Although it happens rarely and has no harmful consequences (besides the error messages), it is undoubtedly a critical error that must be addressed immediately with the highest priority. This problem will be fixed in the next version, which I'll release in a few days.

Thank you for reporting this problem, and sorry for the inconvenience.
Juan Conejero
PixInsight Development Team
http://pixinsight.com/

Offline jtalbot

  • PixInsight Enthusiast
  • **
  • Posts: 75
    • View Profile
    • http://www.starscapeimaging.com
Re: PixInsight 1.8.6 critical signal violations in Process Console
« Reply #2 on: 2019 January 11 11:25:04 »
Hi Juan,

Thats excellent news.  1.8.6 has been working and hasn't crashed but glad you were able to find the bug.

Best Regards,

Jon
Clear Skies

Jon