PCL WIN32 System Exception

[terry0905]

I followed the instructions about uninstalling, resetting and installing the new version, but now, when closing FITS files I have started getting errors where the box says a PCL WIN32 System Exception. The first error says:

At address 0000000060B523C3 with exception code C0000005 :
Access violation: invalid memory read operation at address FFFFFFFFFFFFFFFF

and sometimes there is a second (which follows immediately after the first) which says:

At address 0000000060B523C3 with exception code C0000005 :
Access violation: invalid memory read operation at address 0000000000000E32

It doesn't do it with every file, and is not at all consistent. Also, it doesn't seem to impact on the operation of the program as far as I can see,

The installation file was PI-windows-x86_64-01.07.04.0759-nsi-20111228-c.exe and it is installed on a 64-bit Windows laptop with 8GB of RAM and an Intel i3 processor.

Anyone else seen this or have I just done something wrong - I have to say the WIN32 thing really puzzles me.

Terry

[terry0905]

Some further information - uninstalling and reverting to the previous version of Pixinsight makes the error go away. Re-installing the new version brings the problem back again so it definitely appears to be related to the new version. I guess it's back to the previous version for now.

Terry

[Juan Conejero]

Hi Terry,

This has not been reported before.

I followed the instructions about uninstalling, resetting and installing the new version

The correct order is 'uninstall, install, reset'. It is version 1.7.4 what should be reset. However, this doesn't justify the problem you're getting, so something more---and something really weird---is happening.

Just to start understanding something, could you upload one of the FITS files where you're getting the problem?

[terry0905]

Hi Juan,

I'm new to all this, so is there somewhere that I can upload a file to on the Pixinsight website, or do I need to use some other method (in which case I'll need to set something up).

Just as a piece of additional information, though, I have 1.7.4 installed on a Windows XP Pro 32-bit machine with 4 GB RAM installed (a Dell D630) and it has the same problem with some files. However, on this machine sometimes Pixinsight also then crashes and once I had an "Out of memory" message. However, the 64-bit version at home is my workhorse, so I will concentrate on that for now and will post one of the files that causes problems with it.

Thanks

Terry

[terry0905]

Hi Juan,

I have mono files taken with Ha and OIII which are about 8 MB each and they present no problems, but when combined as an RGB image and cropped at around 22 MB, it has this problem virtually all the time. However, it is 22 MB, so where do I upload it to?

Hi Terry,

This has not been reported before.

I followed the instructions about uninstalling, resetting and installing the new version

The correct order is 'uninstall, install, reset'. It is version 1.7.4 what should be reset. However, this doesn't justify the problem you're getting, so something more---and something really weird---is happening.

Just to start understanding something, could you upload one of the FITS files where you're getting the problem?

Oh, and I reset settings after installing 1.7.4 but to no effect.

Thanks

Terry

[jmasin1]

Hi all,

New here... in the middle of my 45 day PI trial eval, and I have this exact problem.  I am unable to save ANY FITS file without this error.  I can open, I can save TIFF...  but any time I try to save a FIT file I get this error.

I am working on a FIT file from another program (ImagesPlus) but have gone through a number of steps (histogram, DBE etc.) and if I try to save to a new file I get this.

Extremely frustrating...

Win 7, 64-bit, 8G RAM, AMD triple-core
PI Version:  01.07.05.0779 Starbuck (eng x86_64)

Any pointers appreciated, really trying to figure out if I want a full PI license.  It comes highly recommended from CloudyNights.com, but this is a roadblock.

Thanks,
Jon

[Juan Conejero]

Hi Jon and Terry,

The only way I can analyze this problem is by working with one of the FITS files that are giving you problems. As your can imagine we are reading and writing lots of FITS files all the time on all platforms, without any of the problems that you're describing here.

To fix this problem we need to reproduce it on our machines. Could you upload one of these images somewhere? Unfortunately we have had to suspend the new PixInsight Files service temporarily. Do you have something like a Dropbox account or something similar?

Just to rule out one possibility: are those FITS files compressed? FITS compression uses nonstandard schemas that could cause problems with our FITS support routines. If this is the case, we strongly discourage using CFITSIO's compressed modes and do not support them.