Constant crashes. At my wits end now with PI.

[stevek]

Hi, I am still no closer to getting these crashes sorted out and C000005 Win32 exceptions.  No other piece of software causes any issue on my rig at all.  Latest drivers from NVidia, all Windows 10 hot fixes applied. 32G of RAM i7-8700k no overclocks at all.  I use this machine all the time for Photoshop, Premiere Pro and After Effects and C++ development.  NO issues at all.

It is always Pre-processing tasks that tip it over.  Stuff like Blink and Image Integration.

I am sadly about to abandon PI after using it since 2013 and move to APP.  PI is too unstable.

Is there anything else I can try please?  Machine used to work perfectly until 1.8.8 releases.  I have uninstalled multiple times.

[stevek]

I read OpenGL may be responsible so I am goign to try:

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

Edit: Nope didn't work.  I give up with it.  I can crash it almost at will.

[stevek]

Here is a video I made of the crash:

https://youtu.be/c68uPhfQlNA

[John_Gill]

Hi,

I looked at the video but could not read the PixInsight crash info. Can you capture the "red" text and post that info here.  I saw someone commented in your video that you were running Windows10 in 32bit mode.  Can you confirm this.  Find "Control Panel" ---> "System"  This will give exact Window configuration.  If you are in fact running in 32bit mode, that would explain the crash.

space is not black
John

[stevek]

Hi,

I looked at the video but could not read the PixInsight crash info. Can you capture the "red" text and post that info here.  I saw someone commented in your video that you were running Windows10 in 32bit mode.  Can you confirm this.  Find "Control Panel" ---> "System"  This will give exact Window configuration.  If you are in fact running in 32bit mode, that would explain the crash.

space is not black
John

Thanks , I will do when I am in front of the computer.  The computer is Windows 10 x64 bit with 32G of RAM.

[stevek]

*** Backtrace Information ***
================================================================================
  0:  in module: C:\Program Files\PixInsight\bin\PixInsight.exe at address: 0x0
  1: _C_specific_handler in module: C:\Program Files\PixInsight\bin\VCRUNTIME140.dll at address: 0xCA1BB860
  2: is_exception_typeof in module: C:\Program Files\PixInsight\bin\VCRUNTIME140.dll at address: 0xCA1B22E0
  3: is_exception_typeof in module: C:\Program Files\PixInsight\bin\VCRUNTIME140.dll at address: 0xCA1B22E0
  4: is_exception_typeof in module: C:\Program Files\PixInsight\bin\VCRUNTIME140.dll at address: 0xCA1B22E0
  5: _CxxFrameHandler3 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140.dll at address: 0xCA1BC100
  6: _chkstk in module: C:\Windows\SYSTEM32\ntdll.dll at address: 0xE1874660
  7: RtlWalkFrameChain in module: C:\Windows\SYSTEM32\ntdll.dll at address: 0xE17D3730
  8: KiUserExceptionDispatcher in module: C:\Windows\SYSTEM32\ntdll.dll at address: 0xE18734C0
  9: QWidget::windowHandle in module: C:\Program Files\PixInsight\bin\Qt5Widgets.dll at address: 0x89236240
 10: QAccessibleWidget::window in module: C:\Program Files\PixInsight\bin\Qt5Widgets.dll at address: 0x8940A0E0
 11: QAccessibleWidget::window in module: C:\Program Files\PixInsight\bin\qt-plugins\platforms\qwindows.dll at address: 0x8940A0E0
 12: QAccessibleWidget::window at address: 0x8940A0E0
 13: QAccessibleWidget::window at address: 0x8940A0E0
 14: QAccessibleWidget::window at address: 0x8940A0E0
 15: QApplicationPrivate::notify_helper in module: C:\Program Files\PixInsight\bin\Qt5Widgets.dll at address: 0x891F8F80
 16: QApplication::notify in module: C:\Program Files\PixInsight\bin\Qt5Widgets.dll at address: 0x891F63F0
 17: QApplication::notify in module: C:\Windows\system32\UIAutomationCore.dll at address: 0x891F63F0
 18: QApplication::notify at address: 0x891F63F0
 19: QApplication::notify at address: 0x891F63F0
 20: QApplication::notify at address: 0x891F63F0
 21: QApplication::notify at address: 0x891F63F0
 22: QApplication::notify at address: 0x891F63F0
 23: QApplication::notify at address: 0x891F63F0
 24: QAbstractDeclarativeData::setWidgetParent in module: C:\Program Files\PixInsight\bin\Qt5Core.dll at address: 0x88B85C00
 25: QAbstractDeclarativeData::setWidgetParent at address: 0x88B85C00
 26: QAbstractDeclarativeData::setWidgetParent at address: 0x88B85C00
 27: QAbstractDeclarativeData::setWidgetParent at address: 0x88B85C00
 28: QAbstractDeclarativeData::setWidgetParent at address: 0x88B85C00
 29: QAccessibleWidget::isValid in module: C:\Program Files\PixInsight\bin\Qt5Widgets.dll at address: 0x89409100
 30: QAccessibleWidget::window in module: C:\Program Files\PixInsight\bin\Qt5Widgets.dll at address: 0x8940A0E0
 31: QAccessibleEvent::accessibleInterface in module: C:\Program Files\PixInsight\bin\Qt5Gui.dll at address: 0x88BE3780
 32: QAccessibleEvent::accessibleInterface at address: 0x88BE3780
================================================================================
*** PCL Win32 System Exception: At address 00007FFD89236240 with exception code C0000005 :
Access violation: invalid memory read operation at address 0000000000000008

[stevek]

And another video I just did of my Configuration.

https://www.youtube.com/watch?v=-TR0JzfQ1HA&feature=youtu.be

May still be being rendered by YouTube, I only just uploaded it.

Windows 10 Pro X64

In short.
i7-8700k
32G memory
Nvidia 1060Ti

All latest drivers and no overclocks.

Samsung EVO 870 2TB SSD

All lastest patches and updates to OS and PI.

No issues with any other very CPU and memory intensive software.

[Juan Conejero]

Hi Steve,

This is now a confirmed bug on Windows. Unfortunately, it is happening on one of our Windows working machines after a recent Windows 10 update. I am not sure which update, but this problem can be reproduced at least during this week (we don't use Windows regularly, so I can't be sure). The machine has an AMD graphics card so this doesn't look like a problem related to graphics drivers. The crash originates in Qt code (several member functions of QStyleSheetStyle, mainly unpolish()).

Interestingly, we can only reproduce this problem with the Blink tool. It happens when the tool is reset to a default state by clicking the "Close all images" button, just as you show on your video. There are no problems at all with other tools and elements of the user interface. On our working and testing Windows machines everything is stable as always, except Blink. There is nothing special in Blink that could cause this, and in fact the problem does not originate in Blink's code, although this tool is leading to it indirectly, and consistently. There are no problems at all on the rest of platforms; this only happens on Windows. I have no explanation for this.

Naturally, I am working to get this problem fixed as soon as possible. This is out of my control because it does not happen in my code. In these cases I always try to prevent the problem from happening by modifying the code that triggers it, but I am failing completely in this case, since there is nothing I can do to stop the crash (besides not showing any windows on the screen, which obviously is not an option). So the only thing I can do for now is finding a version of Qt where this does not happen, in case it exists, and use it just for the Windows version of PixInsight. I am working on this right now.

I am very sorry for this problem and will try to do my best to get it fixed. Please feel free to use other tools if they can meet your needs better.

[stevek]

I will do anything I can do to help Juan.  My comment about using other tools is not meant as a threat or a swipe Juan, more of a necessity because PI tips over so much on my system.  WBPP can tip it over as well sometimes, as can Image Integration.

I think you need some PI defensive code to protect PI from crashing from whatever exists in Qt that is tipping PI over.

I know you will get this fixed and that's why I am persevering.

Steve

[Juan Conejero]

I cannot reproduce this problem with any other tool or script; just with Blink on Windows 10.

There is no defensive thing to do here. The problem is happening (at least for me) after one of the latest Windows 10 updates, which I cannot identify (there have been quite a few), and is happening in third-party code on which PixInsight depends completely. PixInsight 1.8.8-4 was perfectly stable on this machine before that.

I have been trying with Qt 5.12 instead of 5.13 and no luck, the same problem happens. Thank you very much for your support but I'm afraid this is not going to be easy.

[Juan Conejero]

Steve,

Could you please try the following:

* Run the application with OpenGL software emulation:

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

Let me know if this fixes these problems. It seems to fix all of them on my Windows machine that is causing problems. The drawback of this setting is that screen painting is slower.

* Open the application normally (no command line parameters), then:

- Select EDIT > Global Preferences from the main menu.

- On the Preferences tool, select the Special GUI Effects section.

- Disable the following graphical effects: Translucent workspace top-level windows, Animate AutoHide windows, Translucent AutoHide windows, Fade workspaces.

- Click Apply Global or press F6.

Now please check if the problems are gone. You can check also disabling Translucent workspace child windows. I have evidence that the issues might be caused by windows translucency effects after one of the latest Windows 10 updates.

[stevek]

Hi Juan, I will take a look later on then, I have not been at home to test your idea yet.
Regards, Steve

[Juan Conejero]

Hi Steve,

Never mind. I have fixed this problem and will release a new 1.8.8-5 version in a few days.

I'm going to contact you privately to send you a working version of the core executable for testing, so we can be sure that the solution found works for you. I make this offer extensive to all users who have been suffering these problems on Windows.

[stevek]

Will do Juan, many thanks.  I am away for the weekend - in Malaga (my favoirite place in thew world!).  I'll give this a try on Monday.
Rgds, Steve

[stevek]

.....I have lots of preprocessing to do so will be ablr to test it thoroughly.  I hasten to add that I have only even seen PI tip over with the preprocessing tasks.  Never from the integrated LRGBHaOIIISII masters onwards.