SubframeSelector causes PI crash

[wetcoaster]

I frequently get this error message when processing subs.
<* failed *>
*** PCL Win32 System Exception: At address 00007FF9E7C25470 with exception code C0000005 :
Access violation: invalid memory read operation at address 0000000000000008

Sometimes I get a notification of an error and choose to continue. It occurs with the latest updates to Win10 and the latest version of PI. I chose to back off to version 1.08.06.1447 but the problem did not go away.

A techie friend says that an exception code C0000005 refers to an app trying to access memory that it is not authroirized, e.g., de-allocated memory.

I am running another SubframeSelector on my main laptop and it just crashed with the exactly the same notification except the address is 00007FF9EFC25470 - one hex digit different.

My ASUS Q503 has 8GB RAM.

I will run the same subs on this smaller/older laptop with PI version 1.08.03.1123. It will be much, much slower to process this session.

[wetcoaster]

More info. When I was running a Rescale function tonight the problem occurred twice but the function kept on running after posting an error message each time. Two subs were lost. Therefore the problem is not with a specific PI function. I have a 13" Samsung Ultrabook which has 8GB RAM. I ran a 126 sub session, that had crashed on my bigger system, on the UB. It took 2.5 times as long but finished without a problem. At this point I wondered if my latest version of PI had been corrupted. I uninstalled it, restarted my big laptop, and reinstalled the latest PI version. I then reran the Recale function using the same images from the run with problems and it ran fine. It's too early to say whether the problem is fixed, but one can always hope.

[Juan Conejero]

None of these problems can be reproduced under normal working and testing conditions, on any supported platform. Please provide a data set and a list of steps to reproduce these issues consistently.

In virtually all cases, these problems on Windows are being caused by defective graphics drivers. This is a relatively common issue on Windows with integrated Intel graphics drivers, which do not provide a valid OpenGL implementation. If this is what happens, the only valid solution to this problem can be updating your graphics drivers to the latest version available for your machine and Windows version.

[wetcoaster]

Thanks Juan. I have circumvented the problem for now by going back to a previous version, 1.08.05.1353. I've run hundreds of images through that version without a problem.

I will update my driver(s) and see what happens.

Don

[JB Gayet]

Hi Juan

I have a similar configuration (ie very recent laptop HP Envy) and updated the Nvidia drivers, but I still have the same message plus more and more frequent crashes of PI to desktop with SFS (I have no error message)....