Cosmetic Correction "Real-Time-Preview" produces Access-violation

robwalkmann

Member
Jun 6, 2015
7
0
Preview does NOT work. Changing parameters has no effect in the preview!

>>>> Finally the preview seems to work, but i always get the console message below.

Imaging camera: sbig stf-8300m monochrome ccd camera
Behaviour applies for any "normal" image i have tried so far.



>>>>>>>>>>>>>>>>>>>>>>>>>>> I have installed all available updates on my Windows 10 PC
Installation
Package type : Script
Title : AnnotateImage script version 2.1.2 (bugfix)
Repository : https://pixinsight.com/update/1.8.8-5/
File name : 20200302-script.zip
Release date : 2020-03-02 00:00:00
Install date : 2020-03-21 13:01:09



>>>>>>>>>>>>>>>>>>>>>>>>>>> Console Message >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Reading image:


E:/Astrophotos/Sessions/M51/20200324/c/20_03_24_20_45_M51_FLT=Lum_BIN=1x1_DUR=120sec_TEMP=-20C_0005_c.xisf

Loading image: w=3352 h=2532 n=1 Gray Float32

63 FITS keyword(s) extracted.

** Warning: ProjectionFactory: Invalid/unsupported WCS projection code 'DEF'

Calculate ImageStatistics: done

Create average filtered image...done.

*** PCL Win32 System Exception: At address 00007FF9AC4F7DD6 with exception code C0000005 :

Access violation: invalid memory read operation at address 0000000000000000


*** Backtrace Information ***

================================================================================

0: ¢ in module: D:\Program Files\PixInsight\bin\PixInsight.exe at address: 0x25

1: _C_specific_handler in module: D:\Program Files\PixInsight\bin\VCRUNTIME140.dll at address: 0xEC03B860

2: is_exception_typeof in module: D:\Program Files\PixInsight\bin\VCRUNTIME140.dll at address: 0xEC0322E0

3: is_exception_typeof in module: D:\Program Files\PixInsight\bin\VCRUNTIME140.dll at address: 0xEC0322E0

4: is_exception_typeof in module: D:\Program Files\PixInsight\bin\VCRUNTIME140.dll at address: 0xEC0322E0

5: _CxxFrameHandler3 in module: D:\Program Files\PixInsight\bin\VCRUNTIME140.dll at address: 0xEC03C100

6: _chkstk in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0xF4C81100

7: RtlRaiseException in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0xF4C49EF0

8: KiUserExceptionDispatcher in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0xF4C7FE60

9: KiUserExceptionDispatcher in module: D:\Program Files\PixInsight\bin\CosmeticCorrection-pxm.dll at address: 0xF4C7FE60

================================================================================
 
Last edited:

pfile

PTeam Member
Nov 23, 2009
5,229
57
is this a pre-built machine with windows installed, or was it a "fresh" W10 installation?

what kind of video cards are in the machine? does it have intel integrated graphics?

rob
 

robwalkmann

Member
Jun 6, 2015
7
0
Not a fresh installation.
Current level: Windows 10 Version 1909 Build 18363.720
PI run flawlessly from the beginning on this machine.
No changes in hardware happened.
Graphics NVIDIA GeForce GT 730
 

pfile

PTeam Member
Nov 23, 2009
5,229
57
by "fresh" i was trying to say not-preinstalled by a vendor. some of the pre-installed versions of windows come with a bunch of junk and sometimes competing Qt libraries that PI is not compatible with.

is your graphics driver fully up-to-date?

rob
 

robwalkmann

Member
Jun 6, 2015
7
0
Not preinstalled. I build this PC on my own with a clean W10 setup and as i said, PI ran without problems as of June 2019.
I don't know if there's a common "Real-time-Preview" architecture in PI, but the previews for HistogramTransformation or MultiScaleLinearTransform run without problems.
I checked the driver version and its the latest available.
 

robwalkmann

Member
Jun 6, 2015
7
0
I checked the procedure once again:
the backtrace is created just, when i activate the "Hot Pixels Threshold" checkbox.
 

pfile

PTeam Member
Nov 23, 2009
5,229
57
juan will have to address this; as far as i can tell there is no debug version that's ever been made available. these kinds of problems have been widespread on windows and juan has done everything he could to address them - the problem is/has been bad interactions between Qt (which is a 3rd party UI toolkit that PI relies on) and graphics drivers on windows 10. -5 was supposed to address most of these problems.

at the very least when the next release comes out there's a chance these problems will be fixed...