Segmentation Error / Violation?

Reggie Jones

Hi Adam.  I was using the Image Solver script to plate solve an image so that I can use the SPCC process. As the script was running and obtaining a solution, I received the following error - I do not understand what the problem may be and how to resolve it.  As additional info, I'm running PI version 1.8.9-1 on an iMac running Ventura 13.4.1 if this additional info helps.  Thanks in advance...

Iteration 1, delta = 1.133 as (2.91 px)
Image center ...... RA: 22 29 38.136 Dec: -20 50 16.96
Resolution ........ 0.39 as/px
RMS ............... 0.6281 px (123 stars)
Score ............. 151.1001
******** Error [000]: /Applications/PixInsight/src/scripts/AdP/ImageSolver.js, line 3180: Error: Critical signal caught (11): Segmentation violation

PixInsight 1.8.9-1 - Critical Signal Backtrace
Received signal 11 (SIGSEGV)
Module: 0 PixInsight 0x0000000103e6585d InitializePixInsightModule + 1841965
================================================================================
2: 1 libsystem_platform.dylib 0x00007ff81ccc35ed _sigtramp + 29
1: 2 CoreFoundation 0x00007ff85fb12228 CoreFoundation + 1122095656
================================================================================
*** Error: Critical signal caught (11): Segmentation violation
PixInsight 1.8.9-1 - Critical Signal Backtrace
Received signal 11 (SIGSEGV)
Module: 0 PixInsight 0x0000000103e6585d InitializePixInsightModule + 1841965
================================================================================
2: 1 libsystem_platform.dylib 0x00007ff81ccc35ed _sigtramp + 29
1: 2 ??? 0x00007faa01137430 0x0 + 140368139220016
================================================================================

BlockHead

This is likely a memory problem... likely in RAM memory. 

The technical interpretation of a segmentation error is that a program is accessing memory that is not allocated to it. This could either be because of bad programming (not likely or everyone would be having the issue) or a hardware issue on your machine. There are memory checker diagnostics you can run. 

My guess is you received this error once... but is it repeatable?

-the Blockhead

Reggie Jones

Thanks Adam; I received this error more than once.  When I first got it, I thought the pixel size I was using for the QHY 600M CMOS camera was incorrect - I used the 1x1 binned value instead of the 2x2 binned value that Telescope Live takes it's images at.  When I changed this and reran the Image Solver script, I still received the same error.  

I just went ahead and reran the Image Solver script once more based on your comment and amazingly, it ran perfectly without a problem.  I'll run a memory checker as you've suggested just to look into this further into this but everything seems good at this point.  Once again, I've learned something new.

Thanks Adam and congrats on receiving your 100th APOD award.