Error message when PI shuts down

Kinch

Well-known member
Installed PixInsight Core 1.8.8-6 Ripley (x64) (2020-08-24) and 3 updates.

If I open an image and close again prior to shutting down P.I. I get the following error message:
Capture.JPG


If on the other hand I open PI and then close without opening any image - that error does not appear.

Anything I can do from my side to stop this from happening?
 

Attachments

  • Capture.JPG
    Capture.JPG
    31.7 KB · Views: 60
Disregard the above post....I found the 'cure' for my problem.

The error message stopped appearing on shutdown once I ticked the "Run as Administrator" in the advanced properties for the PI shortcut on my desktop.
 
The error message stopped appearing on shutdown once I ticked the "Run as Administrator" in the advanced properties for the PI shortcut on my desktop.

Please do not do that. An application like PixInsight must NEVER be executed with administrative privileges, on any operating system. By doing that, you are taking a huge risk because when you run something as 'administrator' the code you are running can do literally anything with your system. A complex and powerful application such as PixInsight exposes a large attack surface that can only be protected when it runs under a regular user account.

As for the problem you are reporting, this is not a bug in PixInsight. This problem is machine-specific and does not happen under normal working conditions. It may be caused by a variety of factors, such as buggy or wrong system updates, wrong device drivers, conflicting third-party applications, malware, etc. To solve this problem, you should seek support elsewhere. See for example this request on Microsoft support forums.
 
Thanks for that feedback Juan. The problem only arose with that latest update of P.I......so obviously I jumped to the conclusion that it was that update itself that caused the error to appear. I will uncheck that box again and investigate further. Again, thanks for that heads-up even though you now have me perplexed as to what might be causing this (as there was absolutely no sign of any other problem coming to the surface other than with that version of P.I.)
 
Update:
Unable to deternine any updates to my system in the last days (other than P.I.) that may have caused the reported problem, I removed 1.8.8-6 Ripley (x64) (2020-08-24) and reinstalled 1.8.8-5 (released Feb.). I again reinstalled the 10 updates that were available for this version.

I went through the simple process of opening a FITS image and then shut down P.I. IDid this a couple of times....and everything was fine - just like it had been prior to loading 8-6.....no error message on closing the software!

I removed 1.8.8-5 and reinstalled 1.8.8-6 with the 3 updates that were required for that. Went through the same simple procedure of opening a FITS image and shutting down P.I. Regardlesss of whether or not I close the image first before shutting down P.I. ...again I get the error message that was reported in the 1st post above.

Again, I have reverted to 1.8.8-5 (with updates) and am back to where I was before 1.8.8-6....no problems showing up whatsoever.

That is as far as I can go with this on my home desktop. I will stick with 1.8.8-5 for now. If my system will work OK with 8-5 I find it hard to believe that it is my system that causes the problem with 8-6 but I cannot be 100% sure on that. My next step is to update my obs laptop to 1.8.8-6 and see what happens out there.

I will report back on how that goes.
 
Further update:
As stated above I went out and updated PI on my Obs laptop to 1.8.8-6. On checking PI with the small test that I had been doing earlier - all went OK.....the program shut down with no error message.

I had to concede that the problem was on the house desktop computer.

On the laptop (Obs) I rarely allow updates but for some reason quite recently I allowed a full batch of software updates including Win 10. However, I noticed that one of the latest (if not the latest) Win 10 update (KB4566782) was still pending. Hmmmm.....I went into the house and removed that update from the desktop.

I then removed PI 1.8.8-5 and installed 1.8.8-6 again. On going through the previous test I was doing (opening a FITS image and closing PI) - all went well (several times) - no error message.

So - the problem appears to be Win update (KB 4566782). What I am not sure about is whether or not is was just a bad (corrupt) install or whether or not even a good update install will cause me problems again. I will sit it out for perhaps a week. If nobody else reports problems with KB4566782, then I might try installing it again.

Thanks Juan for nipping my 'easy' solution in the bud....as you say, I may have done more damage than I had anticipated by allowing PI to load with Admin privilages. At least now I know where the problem lies....
 
Thank you so much for the feedback. Unfortunately, Windows updates can be buggy and sometimes even catastrophic, or cause conflicts with other critical software components, such as device drivers. This is a Windows idiosyncrasy. If you reinstall the update in question, the same problem will probably come back. On other machines the same update may not cause any problems. Go figure.
 
What to do :unsure:. As I said....I will sit it out for a week or so (no win updates) and then maybe try again .... unless it procomes apparant that it is a widespread problem amongst PI users.
 
This problem has never been reported before, and we have not received other similar report for the current version. All of our Windows machines are always up-to-date with the latest updates installed, and this obviously does not happen.
 
Something similar happens on my system: W10 2004 64 bit with all updates. PixInsight 1.8.8-5 works fine, but 1.8.8-6 always crashes on termination. I just have to start and then exit PixInsight to reproduce this issue.

If I run PixInsight under WinDbg, it catches the following exception on thread CrBrowserMain:

(f90.2d70): C++ EH exception - code e06d7363 (first chance)
(f90.a18): Unknown exception - code c0000602 (!!! second chance !!!)
KERNELBASE!RaiseFailFastException+0x15c:
00007ffc`9e5eb3cc 0f1f440000 nop dword ptr [rax+rax]
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Program Files\PixInsight\bin\Qt5WebEngineCore.dll -
0:000> k
# Child-SP RetAddr Call Site
00 0000008a`759fc230 00007ffc`9b642f76 KERNELBASE!RaiseFailFastException+0x15c
01 0000008a`759fc810 00007ffc`9b642ef3 CoreMessaging!Cn::FailFast::Do+0x82
02 0000008a`759fc840 00007ffc`9b64304b CoreMessaging!Cn::FailFast::Do+0xb
03 0000008a`759fc870 00007ffc`9b5eafdd CoreMessaging!Cn::FailFast::IndexOutOfRange+0xb
04 0000008a`759fc8a0 00007ffc`9b5d1559 CoreMessaging!Cn::Com::NativeEntry::NoContext_Prologue+0x33d
05 0000008a`759fc9b0 00007ffc`8f8b599a CoreMessaging!Microsoft::CoreUI::IExportMessageSession$X__ExportAdapter::CloseEndpoint+0x49
06 0000008a`759fca50 00007ffc`8f8b5734 textinputframework!TextInputHostAdapter::Dispose+0x4a
07 0000008a`759fca80 00007ffc`8f8b5624 textinputframework!TextInputHost::~TextInputHost+0xe4
08 0000008a`759fcb10 00007ffc`8f8d7a83 textinputframework!TextInputHost::`vector deleting destructor'+0x14
09 0000008a`759fcb40 00007ffc`a05fb7fa textinputframework!Microsoft::WRL::Details::RuntimeClassImpl<Microsoft::WRL::RuntimeClassFlags<2>,1,0,0,IRemoteTextInputHost,ITextInputHost,IMessageProxyReconnectAdapterOwner,IMessageProxyListener,ITextInputHostPrivate>::Release+0x33
0a 0000008a`759fcb70 00007ffc`a05fb494 MSCTF!CThreadInputMgr::~CThreadInputMgr+0x336
0b 0000008a`759fcbc0 00007ffc`a0620717 MSCTF!CThreadInputMgr::`vector deleting destructor'+0x14
0c 0000008a`759fcbf0 00007ffc`3c624dd2 MSCTF!CThreadInputMgr::Release+0x67
0d 0000008a`759fcc20 00007ffc`3c624ee8 Qt5WebEngineCore!GetHandleVerifier+0xc6d552
0e 0000008a`759fcc70 00007ffc`3be662db Qt5WebEngineCore!GetHandleVerifier+0xc6d668
0f 0000008a`759fcca0 00007ffc`3b96b347 Qt5WebEngineCore!GetHandleVerifier+0x4aea5b
10 0000008a`759fccd0 00007ffc`a09e7b3d Qt5WebEngineCore!QWebEngineUrlSchemeHandler::qt_metacast+0x5b557
11 0000008a`759ff520 00007ffc`a09e7c1f ntdll!LdrpCallInitRoutine+0x61
12 0000008a`759ff590 00007ffc`a0a13cac ntdll!LdrpCallTlsInitializers+0x87
13 0000008a`759ff610 00007ffc`a0a13b5d ntdll!LdrShutdownProcess+0x12c
14 0000008a`759ff710 00007ffc`9f87e04b ntdll!RtlExitUserProcess+0xad
15 0000008a`759ff740 00007ffc`9e24ffdc KERNEL32!ExitProcessImplementation+0xb
16 0000008a`759ff770 00007ffc`9e24fe7f ucrtbase!exit_or_terminate_process+0x44
*** ERROR: Symbol file could not be found. Defaulted to export symbols for PixInsight.exe -
17 0000008a`759ff7a0 00007ff6`ed52f428 ucrtbase!common_exit+0x6f
18 0000008a`759ff7f0 00007ffc`9f876fd4 PixInsight!InitializePixInsightModule+0x232958
19 0000008a`759ff830 00007ffc`a09fcec1 KERNEL32!BaseThreadInitThunk+0x14
1a 0000008a`759ff860 00000000`00000000 ntdll!RtlUserThreadStart+0x21


The exception probably happens in Qt5WebEngineCore!DllMain function. Maybe it tries to clean up some stale resources but fails to do so because the process is already in a non-functional state (terminating).

Juan, do you have WinDbg installed as a postmortem debugger on your Windows machines?
 
This problem has never been reported before, and we have not received other similar report for the current version. All of our Windows machines are always up-to-date with the latest updates installed, and this obviously does not happen.

Here is a similar report. Exiting 8.1.1-6 on my Win 8.1 PC always gives me the "program has stopped working" dialog.

This exact problem occurred with with release 1.8.8-3, and I and several others reported it then..

Back then, you released a special installer that solved the problem with 1.8.8-3. Can you release one that fixes it with 8.1.1-6?

Thanks.

--- Mike
 
I cannot reproduce this problem on any of our Windows 10 machines. PixInsight 1.8.8-6 runs and exits without problems on all of them, all the time. These are machine-specific issues.

Kinch, I have just checked that we have KB4566782 installed on all of our Windows machines. It was installed on 8/14/2020. We also have the latest feature update to Windows 10, version 2004, which installed 8/11/2020.

Mike, Windows 8.1 is not supported by current versions of PixInsight.
 
Kinch, I have just checked that we have KB4566782 installed on all of our Windows machines
Yes - (for the record) I foundout this morning that it is NOT Win Update KB4566782 that is causing me the problem. This morning the problem as reported in the 1st post on this thread reappeared.....so I am now going to let Win install that KB4566782......nothing gained by not having it it seems.

It still baffles me why 1.8.8-5 has no problem (nor does any other software programme on my computer) but 1.8.8-6 does. :unsure:
 
Different third-party libraries is the answer to the first question. Version 1.8.8-6 uses Qt 5.15.0 and 1.8.8-5 uses Qt 5.12.7. As for the second question, PixInsight is a large and complex software platform. It has many components that are demanding of system correctness and compliance with declared standards, including a complete web browser component (Chromium). On the other hand, PixInsight is not a typical Windows application. It is a cross-platform project and Windows is not (by any stretch of the imagination) one of its reference operating systems.
 
Just to let you know I am also experiencing this error on shutting down PI on a Windows 10 (1909) machine.
I am using a trial version of the software and this issue is putting me off purchasing the software once the trial expires.
 
I am getting a constant crash of PI on exit. Only with 1.8.8.6/1.8.8.7, on 1.8.8.5 it all works normal.
Running on Asrock 570x mobo with 3700x 32gb Win 10 up to date.
 
As noted above, these problems cannot be reproduced under normal working conditions on any supported platform. These are machine-specific issues unless you can provide a repeatable pattern, or a data set where these problems can be reproduced consistently.

I would consider a complete, clean reinstall of Windows 10 to solve these issues. Also make sure you have the latest versions of all device drivers installed.
 
I have the same Problem as User "Kinch". After installing PixInsight Core 1.8.8-7 Ripley (x64)
and open and then close PixInsight, I get the following error message on my Desktop-PC:

Pixinsight_Fehler01.png

Operating-System is Windows 10 Pro (1909) and the Report of the Eventmanager is as follows:
-----------------------------------------------------------------------------------------------------
Protokollname: Application
Quelle: Application Error
Datum: 25.11.2020 17:27:03
Ereignis-ID: 1000
Aufgabenkategorie:(100)
Ebene: Fehler
Schlüsselwörter:Klassisch
Benutzer: Nicht zutreffend
Computer: hugo-pc
Beschreibung:
Name der fehlerhaften Anwendung: PixInsight.exe, Version: 1.8.8.6, Zeitstempel: 0x5f440022
Name des fehlerhaften Moduls: Qt5WebEngineCore.dll, Version: 5.15.0.0, Zeitstempel: 0x5f0ef522
Ausnahmecode: 0x80000003
Fehleroffset: 0x00000000018f52c9
ID des fehlerhaften Prozesses: 0x544
Startzeit der fehlerhaften Anwendung: 0x01d6c343f42ee556
Pfad der fehlerhaften Anwendung: C:\Program Files\PixInsight\bin\PixInsight.exe
Pfad des fehlerhaften Moduls: C:\Program Files\PixInsight\bin\Qt5WebEngineCore.dll
Berichtskennung: 130f12cd-4a01-4a72-a2df-ef523cb87bb2
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-11-25T16:27:03.624918300Z" />
<EventRecordID>58797</EventRecordID>
<Channel>Application</Channel>
<Security />
</System>
<EventData>
<Data>PixInsight.exe</Data>
<Data>1.8.8.6</Data>
<Data>5f440022</Data>
<Data>Qt5WebEngineCore.dll</Data>
<Data>5.15.0.0</Data>
<Data>5f0ef522</Data>
<Data>80000003</Data>
<Data>00000000018f52c9</Data>
<Data>544</Data>
<Data>01d6c343f42ee556</Data>
<Data>C:\Program Files\PixInsight\bin\PixInsight.exe</Data>
<Data>C:\Program Files\PixInsight\bin\Qt5WebEngineCore.dll</Data>
<Data>130f12cd-4a01-4a72-a2df-ef523cb87bb2</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
-----------------------------------------------------------------------------------------------------
--- end of eventreport ---

The same Error occurs with PixInsight Core 1.8.8-6 Ripley (x64).
On my Laptop with same Operating-System and almost identical environment
and PixInsight Core 1.8.8-7 Ripley (x64) installed, the Error doesn't appear!?

I have uninstalled PI 1.8.8-7 and installed PI 1.8.8-5 on my Desktop-PC and all
works fine, no Error - no Problem.

kind regards
Dietmar
 
Back
Top