Access Violation with Automatic Background Extraction

[wboeck]

I am having problems with Automatic Background Extraction. I am using windows 7- 64 bit with the latest version of PixInsight. I keep getting an access violation when using ABE. It used to work with older versions of PI.

[Carlos Milovic]

Just to try one thing: could you add a pedestal to you image, and see if this happens again?

[wboeck]

I have never added a pedestal before.  I use Batch preprocessing for my images. Do I add a pedestal in BPP?

[Juan Conejero]

If you want to help me diagnose and fix these problems, please try the following:

1. Download the following zip file:

https://pixinsight.com/update-test/20150827-corelibs.zip

2. Uncompress it on any folder.

3. Copy all files extracted in step 2 to the following folder, replacing existing files and folders:

C:\Program Files\PixInsight\bin

You'll need administrative rights to do this. If you have installed on a nonstandard location, change "C:\Program Files\" as appropriate.

Let me know if this patch fixes all of these issues with version 1.8.4 on Windows.

[wboeck]

Thanks. . I will try this tomorrow night

Wayne

[wboeck]

I installed the patch and it still gives the same access violation error. I also added a pedestal and I still get the same error.

Wayne

[wboeck]

I tried the PI version 1.08.03.1123 (x64) on my Laptop without adding a pedestal and Automatic Background Extraction worked. The version on my desktop is 1.08.04.1171 (x64)

[Philippe B.]

No access violation here but I saw a problem where a new result image was not displayed when I select target image correction with normalize and discard background model

The new version of the DLL has corrected this problem

[wboeck]

I uninstalled 1.8.4 and reinstalled 1.8.3 Everything is working again.  I will wait for awhile before trying the update.

[jdupton]

Juan & Wayne,

   I hit this problem for the first time today. I am running 1171 on a Win 8 system with 32GB of memory.

   I have not hit this issue before on 1171 and so did some backtracking to find out why it started happening. The answer for me is that it has to do with the XISF format. After getting an image integration, I saved the image file as both FIT and XISF formats. I closed all other copies of the image and reopened the FIT version. ABE worked fine on the FIT formatted image. I then closed that and opened up the XISF version of the same imahe. ABE consistently throws the "PCL Win32 System Exception" when working with the XISF formatted image. I also played with STF settings to see if it mattered whether STF data was saved with the image. I found no correlation between the STF settings and the ABE exception.

   For me, the work-around is to use FIT format for some operations and convert back and forth as desired to avoid the problem.

   Hopefully, this will help track down the root cause for the bug...


John

[wboeck]

Thanks for the help. I have already reinstalled 1.8.3.  I will wait for more updates before I try it again.

Thanks
Wayne

[danoid]

Ditto - saving the file as a .fit and reloading the .fit and ABE works without system violations.

[wboeck]

Thanks Dan
I may give the new version another try but this should be fixed. Also, I lost all of my process favorites but the reappeared when I reinstalled the previous version.

Wayne