Author Topic: Deleting script icon sometimes causes PCL Win32 System Exception  (Read 3192 times)

Offline mschuster

  • PTeam Member
  • PixInsight Jedi
  • *****
  • Posts: 1087
Maybe one out of ten times, when I attempt to delete a script icon by right clicking and choosing 'Delete Script Icon' from the menu, I see the following PCL Win32 System Exception:

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

Maybe a null pointer or uninitialized variable problem.

PI version 01.07.05.0779 Starbuck (eng x86_64) running on Windows 7.

Offline Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 7111
    • http://pixinsight.com/
Hi,

I can't reproduce this problem on any platform. This should never happen with process icons of any standard process. Absolutely no null pointers or uninitialized variables in PixInsight; in case we have one somewhere, then we have a Priority One bug.

Could you describe the icons where you are seeing this behavior? Or better, could you upload an xpsm file? Thanks!
Juan Conejero
PixInsight Development Team
http://pixinsight.com/

Offline georg.viehoever

  • PTeam Member
  • PixInsight Jedi Master
  • ******
  • Posts: 2132
I find it strange that there is a "PCL Win32 System Exception" on a 64 bit system. Is this as it should be?
Georg (6 inch Newton, unmodified Canon EOS40D+80D, unguided EQ5 mount)

Offline Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 7111
    • http://pixinsight.com/
Yes. Windows' structured exception system is the same on 32-bit and 64-bit platforms. More info here.
Juan Conejero
PixInsight Development Team
http://pixinsight.com/

Offline mschuster

  • PTeam Member
  • PixInsight Jedi
  • *****
  • Posts: 1087
Hi Juan,

Below I am going to give several variations on a procedure to reproduce this error. Please be patient, the problem is intermittent. Sometimes it will take 10 or even 20 or more tries of this procedure to reproduce the problem.

I have attached a script for you to use. Also I have attached screen captures of the exceptions I have seen. The exceptions vary in their addresses. Also please locate the image NGC1808_L.fit from PI's video tutorial to use with this procedure.

1 - Reset PixInsight Settings.
2 - Open PixInsight.
3 - Open NGC1808_L.fit.
4 - Press Cntl-A to invoke the 'STF AutoStretch' command.
5 - In the Script Editor, open the attached script.
6 - In the Script Editor choose the 'Execute -> Compile & Run' command.
7 - Drag the Dialog's New Instance icon to the workspace.
8 - Click the Dialog's Ok button.
9 - Right click the script icon, choose the 'Delete Script Icon' command.

If no system exception occurs, close the mosaic window and repeat steps (6) through (9).

The system exception also occurs in variations of this procedure:

Variation 1: After dragging the New Instance icon to the desktop, click the Dialog's Cancel button and then delete the icon.

Variation 2: Don't open NGC1808_L.fit. Just run the script, drag the icon to the desktop, click Cancel and then delete the icon.

Multiple tries of these procedures will be necessary to see the exception. Sometimes exiting and reopening PixInsight helps to make the problem occur. It is very intermittent, please be patient.

Thanks,
Mike
« Last Edit: 2012 March 20 09:52:07 by mschuster »