Rev 1.8.8.4 on WIndows 10 crash dumps

[k8jb]

For some reason, I get a crash dump with PixInsight 1.8.8.4 on Windows 10 every time I load the program.  Haven't done anything at all except load the program and I get a ~26MB dump.  Everything seems to work OK, just the incessant dumps for no obvious reason!  Can't find anything similar on Linux Mint 19.3.

The Win10 Event Viewer shows:
-------------------------------------------------------------------------------
Faulting application name: PixInsight.exe, version: 1.8.8.4, time stamp: 0x5e1db5eb
Faulting module name: Qt5WebEngineCore.dll, version: 5.13.2.0, time stamp: 0x5dc1834c
Exception code: 0xc0000005
Fault offset: 0x0000000001c3d1c3
Faulting process id: 0xd00
Faulting application start time: 0x01d5d47522694db8
Faulting application path: C:\Program Files\PixInsight\bin\PixInsight.exe
Faulting module path: C:\Program Files\PixInsight\bin\Qt5WebEngineCore.dll
Report Id: 908fff17-257e-4528-a6fa-ef1319ea588c
Faulting package full name:
Faulting package-relative application ID:
--------------------------------------------------------------------------------

Anybody know anything about this?  I suppose I could uninstall/re-install but until I know what the problem is, I'd rather see what others might have found.

John

[k8jb]

More info:  Checked another Win10 machine (new, first PI install) and I get exactly the same crash dumps.

[Juan Conejero]

Hi John,

This does not happen under normal working conditions, and cannot be reproduced on any of our working and testing Windows 10 machines. This problem is being caused by a wrong or outdated graphics driver. Updating drivers to their latest versions available usually fixes these problems. If you are using an integrated Intel HD graphics adapter and your computer has a discrete graphics card (NVIDIA or AMD for example), try disabling the Intel adapter, either from your BIOS if possible, or from Windows. Can you share more characteristics of these machines?

[k8jb]

I'm using a GTX1050 graphics card with the latest drivers.  The only thing I did recently was add 16GB of memory (for a total of 32GB) - both machines have 32GB. The other Win10 machine has an RTX 2080 card in it also with the latest drivers.

Here's a PI benchmark so that should have all the info you asked for:
==================================================
Benchmark version ...... 1.00.08
Input checksum ......... 2cd72b67e12fff2812ef5b5da054ab2a70a25e23
Serial number .......... E7117P7423M52465U24C1IER87CUUXJ2

CPU Identification
CPU vendor ............. GenuineIntel
CPU model .............. Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz

System Information
Platform ............... Windows
Operating system ....... Microsoft Windows 10 Pro
Core version ........... PixInsight Core 1.8.8-4 (x64)
Logical processors ..... 8
Total memory size ...... 31.962 GiB

Execution Times
Total time ............. 01:09.55
CPU time ............... 00:46.22
Swap time .............. 00:23.31
Swap transfer rate ..... 711.162 MiB/s

Performance Indices
Total performance ...... 6763
CPU performance ........ 8189
Swap performance ....... 3939
==========================================================

I'll have to look at the BIOS to disable the Intel HD graphics - assuming its there, can't see it from Windows - unless its hidden somewhere!  I usually use my Linux machine anyway but it's disconcerting to see the crash dumps that I can't stop!

Tnx

John

[k8jb]

If I'm reading the BIOS info correctly, the integrated graphics is already disabled as it should be. 

Only thing I can think of is both machines have 32GB of RAM - more than I ever used before. 

Both machines also use SSDs.

[Juan Conejero]

Hi John,

Your machines look perfectly normal. The problem is being caused by Qt5WebEngineCore.dll, which is part of Qt's QtWebEngine module, and is being used to implement the integrated web browser component of PixInsight. It uses the Chromium browser internally. The most probable cause for Chromium to cause problems is an issue with graphics drivers, but if you have the latest versions installed, then there is nothing else we can do in this regard.

Something that you could try is using desktop OpenGL instead of the default  OpenGL ES implementation:

   C:\Program Files\PixInsight\bin\PixInsight.exe --opengl=desktop

or even a software-based emulation:

   C:\Program Files\PixInsight\bin\PixInsight.exe --opengl=software

Other than that, try to detect some utility applications that might be conflicting with PixInsight, such as a virus protection software or a file management utility, common to both computers on Windows.

[k8jb]

Tnx, I'll try your suggestions. 



HALLELUJAH - we have a solution!  The --opengl=desktop stopped the crashes!  I haven't done any further  regression testing but so far, so good!

What does this tell you???


John

[Juan Conejero]

Hi John,

I'm glad to know it has worked. What does this tell? Well, that Windows is a strange beast. Actually, this is just a confirmation, not a new thing

[k8jb]

AMEN!  That's why my primary machine is Linux!  Tnx again!

[sunlover]

Hi,

FWIW Pixinsight 1.8.8-3 and 1.8.8-4 crash here when I quit the application. I.e. start Pixinsight, wait until it is up and running and then immediately click the top-right close button.
1.8.8-2 is the last version which did not crash.

I have Windows 10 64 bit, AMD Vega 56 graphics card, Ryzen 3950x CPU.

Here is the stack of the crash with 1.8.8-4, which seem to be a NULL pointer dereference:
00007ffd`0a20d1c3 394cd008        cmp     dword ptr [rax+rdx*8+8],ecx ds:00000000`00000179=?
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for PixInsight.exe -
0:000> k
 # Child-SP          RetAddr           Call Site
00 000000bc`4fdfeb40 00007ffd`09882c71 Qt5WebEngineCore!QWebEngineUrlSchemeHandler::qt_metacast+0x4b063
01 000000bc`4fdfeb70 00007ffd`09882ca0 Qt5WebEngineCore!QWebEngineUrlRequestInfo::navigationType+0x8e5e71
02 000000bc`4fdfebb0 00007ffd`0987081d Qt5WebEngineCore!QWebEngineUrlRequestInfo::navigationType+0x8e5ea0
03 000000bc`4fdfebe0 00007ffd`09876896 Qt5WebEngineCore!QWebEngineUrlRequestInfo::navigationType+0x8d3a1d
04 000000bc`4fdfef30 00007ffd`0a471fa4 Qt5WebEngineCore!QWebEngineUrlRequestInfo::navigationType+0x8d9a96
05 000000bc`4fdfef80 00007ffd`0a46ce6c Qt5WebEngineCore!GetHandleVerifier+0x208b54
06 000000bc`4fdff030 00007ffd`0a46cf06 Qt5WebEngineCore!GetHandleVerifier+0x203a1c
07 000000bc`4fdff0e0 00007ffd`0a7e8d43 Qt5WebEngineCore!GetHandleVerifier+0x203ab6
08 000000bc`4fdff180 00007ffd`0a470df5 Qt5WebEngineCore!GetHandleVerifier+0x57f8f3
09 000000bc`4fdff1c0 00007ffd`0a470c54 Qt5WebEngineCore!GetHandleVerifier+0x2079a5
0a 000000bc`4fdff210 00007ffd`0a46b6d4 Qt5WebEngineCore!GetHandleVerifier+0x207804
0b 000000bc`4fdff270 00007ffd`0a46b808 Qt5WebEngineCore!GetHandleVerifier+0x202284
0c 000000bc`4fdff2a0 00007ffd`0a469e8f Qt5WebEngineCore!GetHandleVerifier+0x2023b8
0d 000000bc`4fdff2d0 00007ffd`0988b3ab Qt5WebEngineCore!GetHandleVerifier+0x200a3f
0e 000000bc`4fdff300 00007ffd`0b855779 Qt5WebEngineCore!QWebEngineUrlRequestInfo::navigationType+0x8ee5ab
0f 000000bc`4fdff330 00007ffd`0b85587c Qt5WebEngineCore!IsSandboxedProcess+0x8dd2cd
10 000000bc`4fdff360 00007ffd`0afe7827 Qt5WebEngineCore!IsSandboxedProcess+0x8dd3d0
11 000000bc`4fdff390 00007ffd`0b856582 Qt5WebEngineCore!IsSandboxedProcess+0x6f37b
12 000000bc`4fdff3d0 00007ffd`74599d06 Qt5WebEngineCore!IsSandboxedProcess+0x8de0d6
13 000000bc`4fdff400 00007ffd`74599c2b ucrtbase!<lambda_f03950bc5685219e0bcd2087efbe011e>::operator()+0xa6
14 000000bc`4fdff450 00007ffd`74599be4 ucrtbase!__crt_seh_guarded_call<int>::operator()<<lambda_7777bce6b2f8c936911f934f8298dc43>,<lambda_f03950bc5685219e0bcd2087efbe011e> &,<lambda_3883c3dff614d5e0c5f61bb1ac94921c> >+0x3b
15 000000bc`4fdff480 00007ffd`0ba90f8a ucrtbase!execute_onexit_table+0x34
16 000000bc`4fdff4b0 00007ffd`0ba910b0 Qt5WebEngineCore!IsSandboxedProcess+0xb18ade
17 000000bc`4fdff4e0 00007ffd`766250a1 Qt5WebEngineCore!IsSandboxedProcess+0xb18c04
18 000000bc`4fdff540 00007ffd`7666ab02 ntdll!LdrpCallInitRoutine+0x65
19 000000bc`4fdff5b0 00007ffd`7666a9ad ntdll!LdrShutdownProcess+0x132
1a 000000bc`4fdff6b0 00007ffd`75cccd8a ntdll!RtlExitUserProcess+0xad
1b 000000bc`4fdff6e0 00007ffd`7459ae38 KERNEL32!ExitProcessImplementation+0xa
1c 000000bc`4fdff710 00007ffd`745986ef ucrtbase!exit_or_terminate_process+0x44
1d 000000bc`4fdff740 00007ff7`2cacad60 ucrtbase!common_exit+0x6f
1e 000000bc`4fdff790 00007ffd`75cc7bd4 PixInsight!InitializePixInsightModule+0x1e2b90
1f 000000bc`4fdff7d0 00007ffd`7666ced1 KERNEL32!BaseThreadInitThunk+0x14
20 000000bc`4fdff800 00000000`00000000 ntdll!RtlUserThreadStart+0x21

I confirm that using  --opengl=desktop command line parameter prevents the crash.

Thanks,
Vitali

[stevek]

Tnx, I'll try your suggestions. 



HALLELUJAH - we have a solution!  The --opengl=desktop stopped the crashes!  I haven't done any further  regression testing but so far, so good!

What does this tell you???


John

What did you do to fix?  I also get these crashes.  Also on 32G RAM and disabled the on board graphics. All other apps work fine on this machine.

[Rocketman66]

I've been having issues with my windows computer recently. The system goes into major meltdown and will not respond, leaving me to do a hard shutdown. This corrupts my hard drive.

I've just gone through my system logs to trace the cause. PixInsight is regularly crashing with the same problem as the OP. In fact it's the only program crashing, so I am concerned that PI is the cause of my computer woes.

Below is a sample of the crash log.

Source
PixInsight Core 1.8.8-4 Ripley

Summary
Stopped working

Date
?15/?02/?2020 11:19 AM

Status
Report sent

Description
Faulting Application Path:   C:\Program Files\PixInsight\bin\PixInsight.exe

Problem signature
Problem Event Name:   APPCRASH
Application Name:   PixInsight.exe
Application Version:   1.8.8.4
Application Timestamp:   5e1db5eb
Fault Module Name:   Qt5WebEngineCore.dll
Fault Module Version:   5.13.2.0
Fault Module Timestamp:   5dc1834c
Exception Code:   c0000005
Exception Offset:   0000000001c3d1c3
OS Version:   10.0.18363.2.0.0.768.101
Locale ID:   3081
Additional Information 1:   837c
Additional Information 2:   837c6d3110da25d07e00c2837561ae39
Additional Information 3:   682d
Additional Information 4:   682d72c6794d5cc3bbb8546576372a14

Extra information about the problem
Bucket ID:   98a036e0cabea98ce771b93122fc6b36 (1689334955932150582)