Access violation on STF AutoStretch on Win7 x64

[mc]

I get Access Violation Exception when I push STF AutoStretch button on slope image produced by Linear Fit Clipping in ImageIntegration (download here - image project because PI is not crashing when I save and reopen the image):

PixInsight Core 01.08.03.1123 Ripley (x64)

Unhandled exception at 0x000000013FCB9E9C (PixInsight.exe) in PixInsight.dmp: 0xC0000005: Access violation reading location 0x00000001117FFB24.

RAX = 0000000011800040 RBX = 0000000000859D70 RCX = 00000000FFFFFAE4 RDX = 0000000000000010 RSI = 00000000175D9490 RDI = 000000001996FE70 R8  = 000000000000105C R9  = 0000000000000417 R10 = 000000001D05EBE4 R11 = 000000001996FE70 R12 = 000000000A5F1EFC R13 = 0000000000000003 R14 = 0000000000859D70 R15 = 0000000000000417 RIP = 000000013FCB9E9C RSP = 000000001D05EAC0 RBP = 000000001D05EBC0 EFL = 00010200

PixInsight.exe!000000013fcb9e9c()
PixInsight.exe!000000013fcd580d()
QtCore4.dll!0000000069f4a0ae()
[External Code]

I also captured the dump with heap, but it's quite large (~1.3GB). Please, let me know if more information is needed.

Thanks,
Martin

[Juan Conejero]

Bug confirmed. Thank you so much for the test project, which has helped me to identify and fix the bug very quickly.

The problem is that this slope image contains negative pixel values. A simple workaround to use STF AutoStretch in this case is applying the following PixelMath expression to the image:

max( 0, $T )

Then you can use AutoStretch without problems.

This bug is now fixed in the new version 1.8.4 that we'll release soon. Sorry for the inconvenience.

[mc]

That was quick  . Thanks Juan.

[Juan Conejero]

This problem has been fixed in version 1.8.4. However, the bug fix has been applied to the ImageIntegration tool (negative values are not generated anymore in slope map images), not to the core application. This means that if you open the same image and apply AutoStretch to it in version 1.8.4, you'll get a crash. The reason is that floating point images with values outside the [0,1] range are illegal, and platform stability is not claimed if they are manipulated with any of the tools available. This has been that way since version 1.0 of PixInsight. Checking for out-of-range or invalid numeric values degrades performance of critical application components, so this type of checks are not performed.