New Version Crashing

[jerryyyyy]

Well, this is just not working for me.  After I run it for a while it just crashes.  Never happened with the previous version that I could run for days.  Now I am lucky to have it run for 15 minutes without a crash.  I get this error often.  This is the second release 1448.

This is running on Windows 10 64-bit Dell Precision Mobil Workstation with Xeon processor.  8 Core.

[Juan Conejero]

Hi Jerry,

This problem cannot be reproduced under normal working and testing conditions, on any of our working machines, on any platform.

Today we have conducted a heavy test of PixInsight 1.8.6 on Windows 10 Pro, without any issue. The test has lasted more than 2 hours on the same running instance of the PixInsight core application, and has included interactive work with huge images (some of them occupying 10 GB of RAM) and very long image preprocessing tasks with monochrome CCD and color DSLR raw images, besides many successive executions of the benchmark script. We have stressed the application heavily with many big project load/unload operations. As I have said, zero issues.

The machine where we have made this test is an Apple MacBook Pro 2018 with a 2.9 GHz Intel Core i9 processor, 32 GB of RAM, and a 2 TB SSD hard drive. Windows 10 Pro is running on a Bootcamp partition of 196 GB. The graphics card is an AMD Radeon Pro 560 X with 4 GB of VRAM (the machine also has an integrated Intel HD graphics card, but we have configured Windows to use the AMD card). You can see benchmarks here and here.

We have a machine very similar to yours (a Dell laptop workstation with a Xeon processor and a 4K touch screen). PixInsight 1.8.6 also runs fine on this machine on Windows 10 Pro, but we have had to update the graphics drivers (Intel HD graphics) manually to the latest version.

Have you the latest version of your graphics drivers installed?

[TriplaneDave]

Juan,

Had an instance of PI crashing this a.m. I am not on the same setup as Jerry or you, but have a Surface Laptop.  No external video display, only the built-in display.
It has Win10 version 1809 - build 17763.195
Latest firmware and video drivers installed for Surface Laptop
I have 2 external displays, and the main laptop display.

I was doing a File|Open of 40 xisf images, when PI crashed and closed.  Are there any log files or changes I can make to PI to help trace or debug?

Below is the Windows Event information from event viewer:

Faulting application name: PixInsight.exe, version: 1.8.6.1448, time stamp: 0x5c1aa96b
Faulting module name: ntdll.dll, version: 10.0.17763.194, time stamp: 0xe8b54827
Exception code: 0xc0000374
Fault offset: 0x00000000000faf49
Faulting process id: 0x479c
Faulting application start time: 0x01d4a36f6b8ad8bd
Faulting application path: C:\Program Files\PixInsight\bin\PixInsight.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 37f5a70c-74c0-4814-a800-17f2100c28d8
Faulting package full name:
Faulting package-relative application ID:

[jerryyyyy]

Well, you are courageous enough to install 1809.  I checked with Dell and have the most recent drivers but there is a BIOS update.  I'll do that but there is no indication it is important... security issues.  You know if you do a Microsoft check for updates you generally wind up with 1809.  Two updates ago my system went down hard and had to be reconstructed. 

I may call Dell if I keep getting the error.  Had it once more since this was posted. 

I'll do a full hardware check over lunch. 

[mcintyre_sj]

The latest version is quite regularly crashing on me. I have PI-windows-x64-01.08.06.1448-20181219-c installed on a Windows 10 Asus ROG laptop.

I can't reproduce the crash on demand, but i'd say it's crashed maybe 10 times since installing it a few days ago.

I have been playing with a set of about 50 TIFF and XISF files. I have been doing mostly batchDebayer, dynamicCrops using an imageContainer and the batchStatistics script. And these are the processes that crash. I have not been at the laptop when it crashes. I just return and find PI has closed and there is no trace of why. I restart PI, try again, and then it works.

Is there some log or crash report that provides more info?

[ajs]

A mí también me pasa. Desde la última versión se me ha cerrado unas 6 veces, una de las veces he perdido todo un procesado que estaba a punto de terminar. Antes no me había pasado nunca.

También me pasa que se me quedan dos instancias de Pixinsight abiertas, una es una pequeña ventana sin nada y la otra es el propio Pixinsight.

Me gustaría saber dos cosas:
- ¿Se puede volver a la versión anterior de alguna manera?
- ¿Se puede recuperar el trabajo ante un "crash"? He visto que al inicio aparece un mensaje de Autosave, pero no sé como funciona.

Gracias

[pfile]

creo que la version anterior es en el distribution server. veo la version 1.8.5 alli: dist.pixinsight.com

es posible recuperar parte de su trabajo pero es muy dificil... y no hablo espanol lo suficientemente bien como para explicarlo aqui

Autosave es un "xpsm file" con todos los iconos de proceso antes de un crash. puedes abrirlo con "process > process icons > merge process icons..." (no se que los nombres espanoles estan)

rob

[ajs]

Thank for your answer Rob.
I've found the PROCESS ICON menú, but "mergue" is inactive, but I see "load process icon". Where is the xpsm file?

I'll install the 1.8.5 version, but I want to recovery last working before.

Sorry for my English.

Andres


 

[pfile]

the autosave xpsm file should be in your swap directory. there might be more than one. if there are no process icons loaded on your desktop, then you can use "load process icons" to load the autosave xpsm files.

rob

[ajs]

I can't found any xspm file in the swap directory (in my case is: C:\users\Andres\Appdata\Local\Temp) 

But I can see several files called like this:~PI~J72P7NIW7ZEF0WNH~light_BINNING_1_.swap

[pfile]

sorry - the files will be called <filename>.psm, not .xpsm. i have them in my swap directory...

i am not sure my trick for recovering images from the swap files works anymore - if multiple parallel swap directories are enabled then the problem becomes a lot more difficult. in the past you could just make a new image, do something to it (like invert it) and then copy the latest swap file for the image you want to recover over the new image's swap file, then undo the change to the new image inside pixinsight. that would cause PI to load the changed swap file back from disk and thus recover the image. but i'm not sure how to do it if you have multiple swap file directories turned on like i do now.

rob

[ajs]

I have found only one .psm archive, I open it but has the processes of another picture, not of the last one. I'm afraid that autosave didn't work in the last picture I processed.


I'm installing the 1.8.5 version

Thank you

[pfile]

i believe the autosave file is only saving process icons that have been saved to the PI desktop. i don't think the PSM files contain the state of the different processes.

rob

[ueberlaeufer]

I have a similar error message like TriplaneDave. The event log says:
Name der fehlerhaften Anwendung: PixInsight.exe, Version: 1.8.6.1448, Zeitstempel: 0x5c1aa96b
Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.17134.471, Zeitstempel: 0x7e614c22
Ausnahmecode: 0xc0000374
Fehleroffset: 0x00000000000f47fb
ID des fehlerhaften Prozesses: 0x34dc
Startzeit der fehlerhaften Anwendung: 0x01d4a5f3b4f8299e
Pfad der fehlerhaften Anwendung: C:\Program Files\PixInsight\bin\PixInsight.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\ntdll.dll
Berichtskennung: 3eb9a5bd-961d-4092-bd95-049496f44b8b
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

I am using Windows10, German version.
What I noticed: Uninstall does not remove PixInsight Core. Should we remove this as well before installing the new version?

-Erich

[jerryyyyy]

Well, my version still is crashing regularly.  Did it three times this AM and is close to unusable.  It seems to be getting worse.  I have VisualStudio and invoked the debugger.  I got this:

Unhandled exception at 0x00007FFD0F56849B (ntdll.dll) in PixInsight.exe: 0xC0000374: A heap has been corrupted (parameters: 0x00007FFD0F5CC6E0). occurred. 

I cannot go further, can I get the previous version back?

I very carefully updated all the drivers and the BIOS.