Author Topic: Looping Memory Access Error on Drag-Drop of Batch of RAW Files  (Read 3079 times)

Offline seigell

  • Newcomer
  • Posts: 4
Upon attempting to Open a batch of RAW Files via Drag&Drop onto the main App Window, I'm stuck in a looping Memory Access Error:

At address 0000000000000020 with exception code C0000005 :
Access violation: invalid memory write operation at address 0000000000000020

And, interestingly, but likely cosmetic, the Error Popup "Title" referenced "Win32" Error (on a 64-bit Win7 running a 64-bit App)...

I have been having a problem with 1-2 bad Darks and Bias frames, for which I was going to do a quick STF to identify if any of the subs had a large blocky pattern.

After Terminating PixInsight via TaskMgr (couldn't get PI to Close itself) and restarting, I was unable to repeat with same or other similar set of files.

This is on a Win7 Pro 64 desktop running Ripley v1.8.1.1083.

Offline Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 7111
    • http://pixinsight.com/
Re: Looping Memory Access Error on Drag-Drop of Batch of RAW Files
« Reply #1 on: 2014 January 30 00:13:05 »
I can't reproduce this problem on any platform. Let me know if it happens again.

Quote
And, interestingly, but likely cosmetic, the Error Popup "Title" referenced "Win32" Error (on a 64-bit Win7 running a 64-bit App)...

The Windows structured exception handling APIs are the same on 32-bit and 64-bit versions of Windows. System exceptions (such as memory access violations or invalid instruction execution attempts) are collectively known as "Win32 System Exceptions" on Windows. For example, Microsoft's .NET platform has a Win32Exception class:

http://msdn.microsoft.com/en-us/library/system.componentmodel.win32exception%28v=vs.110%29.aspx

and its name is common to 32-bit and 64-bit versions.
Juan Conejero
PixInsight Development Team
http://pixinsight.com/