Author Topic: Error Message  (Read 2664 times)

Offline mike150iuoe

  • Newcomer
  • Posts: 2
Error Message
« on: 2016 January 11 10:44:30 »
Running 1.8.4.1185
Win 8.1

PCL Win32 Sys Exception@address 00007FF9B46143C8 with exception code C0000005
Access Violation: invalid memory read operation @ address 0000000000000018

This error message occurred while running MLT noise reduction, iteration completed but received this message along with a message to save work and close program and restart.

Reporting as an FYI

Mike

Offline Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 7111
    • http://pixinsight.com/
Re: Error Message
« Reply #1 on: 2016 January 11 11:16:51 »
This is not reproducible on any of our testing machines. Is this a repeatable problem, or has it been a sporadic one?

What is the exact message telling you to save your work and exit?
Juan Conejero
PixInsight Development Team
http://pixinsight.com/

Offline mike150iuoe

  • Newcomer
  • Posts: 2
Re: Error Message
« Reply #2 on: 2016 April 20 15:11:32 »
Sorry for not replying to this earlier as I was just reporting as requested but I have run across something similar today while running deconvolution.
Error Message reads as follows: Pixinsight Error PCL Win 32 System Exception.
Address: 00007FF9DBDF1F08 with exception code C0000005; Access Violation; Invalid Memory Read operation at address 0000000000000018

Requested I save my project and close program, which I did.
This is a first time occurrence, the previous report has only occurred that one time.
Currently running Windows 10 but did not have the latest updates for PI installed at the time (3of them).
I was able to save all my work without an issue.
I had run Deconvolution several times with changing parameters without issue on a preview and was executing on the entire image when this occurred at the
conclusion of the iterations. I missed the first message but it did pertain to the swap files but I did not note the particulars at that time.

I restarted PI and just opened my image and ran Decon  once again with the exact same settings without and issue.
Just the usual gremlins in Windows as far as I'm concerned  :o
I would  classify this as another sporadic issue but just in case
Love this program!
Mike