Cura 4.8.0 crashes during first-time-setup immediately after installation

[JAL741]

I installed Cura 4.8.0. It uninstalled my working Cura 4.7 (during which I chose the options to also remove all profiles) and then installed itself. It then asked me the first-time-setup questions about license agreement and data collection. When it asked me to sign it with an account; I pressed 'skip'. Then it asked me to select my printer; I pressed "non-networked printer". Before the list of printers to choose from was displayed, the application window disappeared completely without warning. Looking in Windows Event Logs, I see the following failure logged:

Faulting application name: Cura.exe, version: 0.0.0.0, time stamp: 0x5f9933ba
Faulting module name: ig4icd64.dll, version: 9.17.10.4459, time stamp: 0x573dfb41
Exception code: 0xc0000005
Fault offset: 0x00000000000011b1
Faulting process id: 0x1a68
Faulting application start time: 0x01d6b84cc744f216
Faulting application path: C:\Program Files\Ultimaker Cura 4.8.0\Cura.exe
Faulting module path: C:\WINDOWS\system32\ig4icd64.dll
Report Id: 575bc833-21a5-4c85-bfdf-5bb239c17d86
Faulting package full name:
Faulting package-relative application ID:

[JAL741]

I have now un-installed Cura 4.8.0, then re-installed it. The crash now happens even before being asked to select a printer.

I have captured a video demonstrating this (attached). I have also attached the entire contents of the %AppData%\Cura folder where I see several log files that developers may find useful.

Cura 4.8.0 installation failure (crash) - 11-Nov-2020.zip

Cura AppData-Roaming files.zip

.

[jellespijker]

Hi @JAL741

Could it be that I asked you on a Facebook comment to report this here? If so. Thank you for your the bug reports and log files. These will be most helpful, but you would make us really happy if you also fill in the bug template next time (lets hope there will be no next time tho). Since that template also contains a question regarding the graphic driver and operating system that you're using.

I haven't look in detail through the logs but the faulting module that is reported by windows is C:\WINDOWS\system32\ig4icd64.dll, which is a part of the Intel Graphics Accelerator Drivers for windows 7.

Can you tell us what videocard and which windows system you are using?

[CGBromley]

I am having same problem but I am using Windows 10, Intel(R) HD Graphics. Can I just go back to 4.7? I don't see where I can download, keeps sending me to 4.8.0

[JAL741]

@jellespijker system information is now attached. Also, what "bug template"? I just clicked the 'log issue" button and it did not present me with any template.

DxDiag.txt
SysInfo.txt

[JAL741]

@jellespijker your suggest that it might be related to the graphics processor in my laptop, reminded me that there are two; the integrated Intel CPU graphics processor, and an add-in nVidia processor. By default, the laptop automatically selects which graphics processor to use, per application. I decided to force Cura.exe to use the nVida graphics processor, and that allowed me to complete the Cura 4.8.0 installation and setup. It is now working for me, but the fact that Cura 4.8.0 crashed in the first place, instead of handling this gracefully, is still a bug in my opinion.

[jellespijker]

@CGBromley Older versions of Cura can be downloaded from https://github.com/Ultimaker/Cura/releases
You can have multiple versions installed along side each other

[jellespijker]

@JAL741 Glad to hear that you have found a work around, and yes you're absolutely correct that this is still a bug. I will ask the developers whom work on Windows to take a closer look, since they're more familiar with this system then I'm.

@konskarm or @rburema could either one of you take a look at this issue please?

@JAL741 pressing the "new issue" button should have presented this screen

[rburema]

Looking through the logs, I see that it somehow detects OpenGL 3.1 with GLSL version 140, and it's running from your Intel card at the time the logs stop:

2020-11-11 10:47:20,170 - DEBUG - [MainThread] UM.Qt.QtRenderer._initialize [210]: Support for Vertex Array Objects: True
2020-11-11 10:47:20,188 - DEBUG - [MainThread] UM.View.GL.OpenGL.__init__ [112]: Initialized OpenGL subsystems.
2020-11-11 10:47:20,196 - DEBUG - [MainThread] UM.View.GL.OpenGL.__init__ [113]: OpenGL Version:  3.1.0 - Build 9.17.10.4459
2020-11-11 10:47:20,203 - DEBUG - [MainThread] UM.View.GL.OpenGL.__init__ [114]: OpenGL Vendor:   Intel
2020-11-11 10:47:20,210 - DEBUG - [MainThread] UM.View.GL.OpenGL.__init__ [115]: OpenGL Renderer: Intel(R) HD Graphics 3000
2020-11-11 10:47:20,218 - DEBUG - [MainThread] UM.View.GL.OpenGL.__init__ [116]: GLSL Version:    1.40.0

So there are 2 issues here:

• Why isn't is selecting your NVidia card when you select that (we can't do much about this).
• Why is it crashing rather than (or after!) selecting the legacy rendering option that should take care of all OpenGL drivers supporting less than 4.1.x? (And a hard crash at that, not even an error report shown.) We've had very hard to debug problems with Intel drivers before (frustratingly, on their side, so we can do little but work around them).

I'm not sure what's wrong, but you could try these things:

• Update the Intel drivers (I'm not sure how recent yours' are).
• Make sure the program _does_ start with the NVidia card.
• Set force_empty_shader_cache under the [view] heading to = True in cura.cfg.

[jellespijker]

Why isn't is selecting your NVidia card when you select that (we can't do much about this).

@rburema The log you're reading was when he was indeed running from the Intel card. Selecting the NVidia card was a work around and then it doesn't crash (therefor no log file provided of that scenario)

[md-hexdrive]

I also have this identical problem, and cura 4.8 also crashes for me at first setup. I haven't seen the log file itself, but my computer only has Intel Integrated Graphics.
I will be moving to an earlier version of cura for now.