Author Topic: PI 1.5.2 Problem  (Read 4585 times)

Offline eddiet

  • PTeam Member
  • Newcomer
  • Posts: 18
    • http://astroshed.com
PI 1.5.2 Problem
« on: 2009 June 15 03:30:53 »
Hi Juan, all

I have a few issues with V1.5.2. I will post them seperately to try and keep things tidy.

The first problem is 100% reproduceable for me, but I imagine that it might be related to me only, or everyone would be mentioning it.

If I start PixInsight, then close it immediately without doing anything, I get a JIT Debugger Error "An Unhandled win32 exception occurred in PixInsight.exe [3232]"

I'm running Win XP Pro 64 on a Quad core machine. Not sure what more info you need, that I can provide. Please let me know. Here is my startup log from the Processing console, if it helps.

Thanks

Eddie

Initializing PixInsight...

JavaScript runtime initialized.

Installing 31 module(s):
C:/PCL64/bin/BackgroundModelization-pxm.dll
C:/PCL64/bin/BMP-pxm.dll
C:/PCL64/bin/CloneStamp-pxm.dll
C:/PCL64/bin/ColorCalibration-pxm.dll
C:/PCL64/bin/ColorManagement-pxm.dll
C:/PCL64/bin/ColorSpaces-pxm.dll
C:/PCL64/bin/Compatibility-pxm.dll
C:/PCL64/bin/Convolutions-pxm.dll
C:/PCL64/bin/Debayer-pxm.dll
C:/PCL64/bin/Deconvolution-pxm.dll
C:/PCL64/bin/DSLR_RAW-pxm.dll
C:/PCL64/bin/FITS-pxm.dll
C:/PCL64/bin/Geometry-pxm.dll
C:/PCL64/bin/Global-pxm.dll
C:/PCL64/bin/GREYCstoration-pxm.dll
C:/PCL64/bin/Image-pxm.dll
C:/PCL64/bin/ImageIntegration-pxm.dll
C:/PCL64/bin/ImageRegistration-pxm.dll
C:/PCL64/bin/IntensityTransformations-pxm.dll
C:/PCL64/bin/JPEG-pxm.dll
C:/PCL64/bin/JPEG2000-pxm.dll
C:/PCL64/bin/MaskGeneration-pxm.dll
C:/PCL64/bin/Morphology-pxm.dll
C:/PCL64/bin/NoiseGeneration-pxm.dll
C:/PCL64/bin/NoiseReduction-pxm.dll
C:/PCL64/bin/NoOperation-pxm.dll
C:/PCL64/bin/PixelMath-pxm.dll
C:/PCL64/bin/RestorationFilters-pxm.dll
C:/PCL64/bin/Sandbox-pxm.dll
C:/PCL64/bin/TIFF-pxm.dll
C:/PCL64/bin/Wavelets-pxm.dll
* Scripting resources updated.
31 of 31 module(s) installed.

Processing script file: C:/PCL64/bin/startup.scp

PixInsight Core 01.05.02.0503 (x86_64)
Copyright © 2003-2009 Pleiades Astrophoto
----------------------------------------------------------------------
Welcome to PixInsight. Started 2009 Jun 15 10:27:15 J2454997.93559 UTC

* Parallel processing enabled: Using 4 logical processors.
* PSM AutoSave enabled. Auto-save period: 30 seconds.
Regards,

Eddie T.
http://astroshed.com

Offline eddiet

  • PTeam Member
  • Newcomer
  • Posts: 18
    • http://astroshed.com
Re: PI 1.5.2 Problem
« Reply #1 on: 2009 June 15 03:44:24 »
Hello again,
I've done some debugging, and switched from JIT to Dr Watson.

The crash is still happening, but we now have some extra information.

AppName: pixinsight.exe    AppVer: 1.5.2.503    ModName: ntdll.dll
ModVer: 5.2.3790.4455    Offset: 000000000003bc0b

Hope this helps. Please let me know if there's anything else I can provide..
Regards,

Eddie T.
http://astroshed.com

Offline Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 7111
    • http://pixinsight.com/
Re: PI 1.5.2 Problem
« Reply #2 on: 2009 June 15 03:52:51 »
Hi Eddie,

I can't reproduce this on Vista x64 SP1 and XP 32 SP3. An "unhandled win32 exception" doesn't tell us a lot about what's happening. This is often an access violation, but could actually be anything.

Let's try to stretch the problem. By "closing immediately", how much time do you mean? Is it different if, say, you wait 30 seconds before closing, or one minute?

Thank you
Juan Conejero
PixInsight Development Team
http://pixinsight.com/

Offline eddiet

  • PTeam Member
  • Newcomer
  • Posts: 18
    • http://astroshed.com
Re: PI 1.5.2 Problem
« Reply #3 on: 2009 June 15 05:32:31 »
Hi Juan,

The length of time seems irrelevant. I just tried several periods. Close immediately after startup. Close after 5 seconds, after 10 seconds. After ten minutes, when I tried the ABE workaround just before.

The result is always the same. After PI closes, I get the error above.

There is a more detailed report that Microsoft wants me to send to them, I can provide this if you can interpret it.
Regards,

Eddie T.
http://astroshed.com