PixInsight Forum (historical)
PixInsight => Bug Reports => Topic started by: jerryyyyy on 2019 January 02 07:27:48
-
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.
-
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 (http://pixinsight.com/benchmark/benchmark-report.php?sn=0169XSRE9Q3A7W7P85FLBTZVCJP7MP5J) and here (http://pixinsight.com/benchmark/benchmark-report.php?sn=80577S2K79UUOHW7I71LX9EDTM5E2Q3L).
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?
-
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:
-
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.
-
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?
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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.
-
Once more with a different error:
Unhandled exception at 0x00000019561FEA30 in PixInsight.exe: 0xC0000005: Access violation executing location 0x00000019561FEA30. occurred
Full output attached:
-
Here is another error message, which produces no crash but is anoying:
Copy from the console:
DynamicBackgroundExtraction: Processing view: IC434_RGB_registered
Writing swap files...
92.912 MiB/s
*** PixInsight API Error: CreateImageWindow(): Low-level API function error (0x0001): Unknown error
Reading swap files...
918.538 MiB/s
<* failed *>
This error occurs here and then. This one was after several times applying DBE. Running DBE a second time produces normal output.
Windows10 1803.
-Erich
-
*** PixInsight API Error: CreateImageWindow(): Low-level API function error (0x0001): Unknown error
This is not reproducible on any of our working and testing machines. Can you please provide a data set and a sequence of operations to reproduce this problem?
-
Once more with a different error:
Unhandled exception at 0x00000019561FEA30 in PixInsight.exe: 0xC0000005: Access violation executing location 0x00000019561FEA30. occurred
Full output attached:
From the report you have attached, I can see several sources of potential problems. One of them is Acronis True Image Shell Extensions. I know you have these extensions installed because the file 'C:\Program Files (x86)\Acronis\TrueImageHome\tishell64.dll' has been loaded. I would uninstall this utility.
Another thing that may cause problems is 'C:\Program Files\Common Files\microsoft shared\ink\tiptsf.dll'. This is part of Microsoft Tablet PC Component. There is a known problem with Ink support in Qt 5.12.0:
https://bugreports.qt.io/browse/QTBUG-72078
This should be fixed with Qt 5.12.1, which I'll include in a new version of PixInsight as soon as possible. However, I doubt this can be causing the kind of problems you are experiencing.
The files under the 'k127370.inf_amd64_40f42c925df30890' folder are the Intel graphics drivers. They are most likely causing all of these problems on your machine. You could try the following:
- Define the following environment variable:
QTWEBENGINE_CHROMIUM_FLAGS=--disable-gpu
- Execute PixInsight from a command line as follows:
C:\Program Files\PixInsight\bin\PixInsight.exe --opengl=software
Let's see if this solves these problems on your machine.
-
Another possibility is:
C:\Program Files\PixInsight\bin\PixInsight.exe --opengl=raster
if the above 'software' option doesn't help.
-
*** PixInsight API Error: CreateImageWindow(): Low-level API function error (0x0001): Unknown error
This is not reproducible on any of our working and testing machines. Can you please provide a data set and a sequence of operations to reproduce this problem?
This is one of these "sometimes" error, which are really difficult to reproduce. I will try to reproduce and provide the data, if possible.
In the meantime I worked with the same instance after my error and after a while I got another error message, when I wanted to switch the workspaces:
PCL Win32 System Exception
At address 00007FFE887A8013 with exception code C0000005 :
Access violation: invalid memory read operation at address FFFFFFFFFFFFFFFF
I have my temp directory still at a system temp dir. But I don't think that this is the root cause (hopefully not my hardware).
-
Thanks for the ideas. I have updated Acronis and turned off the real-time protection. That is the easiest starting point.
The drivers etc. all worked with the prior version (nothing changed).
Unfortunately, I have to use Acronis as it does make a usable disk image. This is a difficult problem as Windows 10 has serious degraded Windows 7 Backup and Restore so that it is no longer reliable. Also, you have to turn off Bitlocker to make the image. All this is a pain but otherwise I have no way to reconstitute a system other than rebuild from scratch.
If you hear nothing, it was Acronis.
-
*** PixInsight API Error: CreateImageWindow(): Low-level API function error (0x0001): Unknown error
This is not reproducible on any of our working and testing machines. Can you please provide a data set and a sequence of operations to reproduce this problem?
I tried to set up an environment, where the errors can be reproduced.
First I changed the temp dir to a separate location to get rid of possible system interference. I took one file, did a dynamic crop, repeated several (about 20 ( more than I usual would do ;-))) runs of DBE and performed a PCC. After that I opened the same file from disk (via drag and drop) again and got an access violation error. PixInsight closed after confirmation (click OK or so) at the error window.
I tried to repeat this error after a next start. It was not exactly repeatable, so I played a little bit with the data but I got another access violation.
A common pattern seems to be that it appears with disk I/O (opening files, writing/reading swap files). Even if I had a problem with my SSD, I would expect that the software can catch errors caused by invalid data.
For really clean tests I would need to restart the computer all the time before starting PI, but I also use it for "real" work in parallel.
Nevertheless I will play around with it to get reproducible results (but I am not a software tester).
On the good side I learned something about the parameters in DBE, as I also tried to play with them to see, if I find a pattern there.
-Erich
-
Well, maybe there are fewer crashes with Acronis turned off but I also get this low level error. Had it three times this am. I'll go over the options but seems like someone else has similar problems.
I am not experienced with windows scripting but when I run:
QTWEBENGINE_CHROMIUM_FLAGS=--disable-gpu
In the CMD window as admin or in powershell I get command unrecognized. I tried it with single quotes. Am I supposed to use a SET command? I tried that and got no error in powerscript. I could then execute:
C:\'Program Files'\PixInsight\bin\PixInsight.exe --opengl=software
with single quotes in Powershell; will see how that goes; will also have to recall how to make this a .bat script... not .txt
I have a:
Xeon E3-1505M Processor
NVIDIA Quadro M1000M and
Intel HD Graphics P530
PS I get what you are trying to do here. I used to program in OpenGL and so you are trying to disable the hardware acceleration for QT and just do the rendering in software. OK, but does that flag disable hardware acceleration for all software?
-
Hello,
Not sure that this will help, but …
I too seem to be having the same problems on my HP Envy laptop running Windows 10. No issues on my desktop.
The most common error messages are shown below. When executing my long-running scripts repeatedly on the same data, the errors occur at random / different times. Running short-duration scripts may not demonstrate the problem.
When examining the Windows Event Viewer, at least one problem does appear to relate to QT. [Post edited, correction]. See log entry below.
For the time being, I am constrained to using only my Desktop for image processing. (Only an issue when I am away from home).
Regards
Dean
Reading image:
….
Loading image: w=3876 h=2883 n=1 Gray Float32
<* failed *>
*** PCL Win32 System Exception: At address 00007FFC71435470 with exception code C0000005 :
Access violation: invalid memory read operation at address 0000000000000008
StarMask: Processing view: TargetImage
Computing intensity component: done
Extracting structures: done
*** PixInsight API Error: CreateImageWindow(): Low-level API function error (0x0001): Unknown error
<* failed *>
Event Viewer Entry (one of many)
Faulting application name: PixInsight.exe, version: 1.8.6.1448, time stamp: 0x5c1aa96b
Faulting module name: Qt5Core.dll, version: 5.12.0.0, time stamp: 0x5c0ffefb
Exception code: 0xc0000409
Fault offset: 0x0000000000028aa8
Faulting process id: 0x1b70
Faulting application start time: 0x01d4ad1f7c05a28b
Faulting application path: C:\Program Files\PixInsight\bin\PixInsight.exe
Faulting module path: C:\Program Files\PixInsight\bin\Qt5Core.dll
Report Id: a2fb8743-0374-46a7-8e9c-ee6e7b9df3c6
Faulting package full name:
Faulting package-relative application ID:
-
Dean
Just to keep things correct, QT is not QuickTime.
https://en.wikipedia.org/wiki/Qt_(software) (https://en.wikipedia.org/wiki/Qt_(software))
Mike
-
Thanks Mike
Quite right. Post corrected above.
Regards
Dean
-
I too get the crash after the 0000000000000008 me meet error. Especially when trying to run the subframe selector script. Other than that it's been running good, just cranked out a 5-hour integration and it didn't crashed when done. I have a Dell XPS 15 32GB of RAM terabyte SSD.
-
My systems seems more stable with the graphics cards turned off as noted for QT. This of course raises the question of what is going on about why I cannot use my $$$ graphics. I have all the latest drivers etc....
-
Just for the record, still intermittently crashing... and the autosave only saves process icons?
-
Hi Jerry,
I'm sorry to read that. Definitely this is a machine-specific issue that we cannot reproduce. Version 1.8.7 is stable on all supported platforms under normal working conditions, including Windows 10.
-
I am getting the same error when I am trying to iconize an image. It has occured after DBE, ABE, and Extract Cie L Component.
I am using a touchscreen enabled All-in-One PC running Windows 10 with an onboard Intel Graphics card. Below is the error message.
If I click on an iconized image in PI this message keeps showing up over and over again and does not open the image. If I randomly click on iconized images then I can access File and Save the Project otherwise I get the error message when clicking on anything while this error is occurring. Like the OP I have not installed any Windows updates or updated any drivers, so I do not understand where this error originated. Everything worked beautifully prior to the last PI update.
*** Backtrace Information ***
================================================================================
0: in module: C:\Program Files\PixInsight\bin\PixInsight.exe at address: 0x1F2535D0
1: _C_specific_handler in module: C:\Program Files\PixInsight\bin\VCRUNTIME140.dll at address: 0x1747B860
2: is_exception_typeof in module: C:\Program Files\PixInsight\bin\VCRUNTIME140.dll at address: 0x174722E0
3: is_exception_typeof in module: C:\Program Files\PixInsight\bin\VCRUNTIME140.dll at address: 0x174722E0
4: is_exception_typeof in module: C:\Program Files\PixInsight\bin\VCRUNTIME140.dll at address: 0x174722E0
5: _CxxFrameHandler3 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140.dll at address: 0x1747C100
6: _chkstk in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0x1F2A10E0
7: RtlRaiseException in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0x1F269EF0
8: KiUserExceptionDispatcher in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0x1F29FE40
9: QWidget::windowHandle in module: C:\Program Files\PixInsight\bin\Qt5Widgets.dll at address: 0xD8C36240
10: QAccessibleWidget::window in module: C:\Program Files\PixInsight\bin\Qt5Widgets.dll at address: 0xD8E0A0E0
11: QAccessibleWidget::window in module: C:\Program Files\PixInsight\bin\qt-plugins\platforms\qwindows.dll at address: 0xD8E0A0E0
12: QAccessibleWidget::window at address: 0xD8E0A0E0
================================================================================
-
9: QWidget::windowHandle in module: C:\Program Files\PixInsight\bin\Qt5Widgets.dll at address: 0xD8C36240
This is a machine-specific issue related to your graphics driver that cannot be reproduced under normal working conditions. This is beyond our control. Are you using the latest version of PixInsight? Integrated Intel HD graphics are known to cause problems, especially on laptops with touch screens. Try after updating your graphics drivers to the latest version available.