Godot Closes when restoring a minimized floating script editor window (Intel driver bug)

[gemmomoh]

Godot version

4.1 - stable

System information

Godot v4.1.stable - Windows 10.0.22621 - Vulkan (Compatibility) - Intel(R) HD Graphics 4400 () - Intel(R) Core(TM) i5-4300U CPU @ 1.90GHz (4 Threads)

Issue description

Godot Closes when restoring a minimized floating script editor window

Steps to reproduce

Enable floating script window

minimize the window and try restoring it.

Recording.2023-07-17.093433.mp4

Minimal reproduction project

Engine based problem

[Calinou]

Do you have the Save on Focus Loss editor setting enabled?

[gemmomoh]

No i don't

…

On Mon, 17 Jul 2023, 10:39 Hugo Locurcio, ***@***.***> wrote: Do you have the *Save on Focus Loss* editor setting enabled? — Reply to this email directly, view it on GitHub <#79575 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZAKVVMV7C7Z6HP3OQRFQPLXQUB43ANCNFSM6AAAAAA2MVQEN4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[iseos]

Same problem, if you minimize the floating scripts window and try to expand it, the editor closes completely.
Windows 10.

[iseos]

I just discovered another strange behavior:
If you make the scripts window float and minimize the main editor window, the entire Godot editor closes.

[iseos]

Windows 10 error logs:

Faulting application name: Godot.exe, version: 4.1.1.0, time stamp: 0x00000000
Faulting module name: ig8icd64.dll, version: 20.19.15.5126, time stamp: 0x5e279465
Exception code: 0xc0000005
Fault offset: 0x00000000001b5426
Faulting process id: 0x2780
Faulting application start time: 0x01d9d7817599bd44
Faulting application path: D:\Apps\Local\Godot4\Godot.exe
Faulting module path: C:\Windows\SYSTEM32\ig8icd64.dll
Report Id: 5cfb2a12-1e41-4deb-9994-b258519a125e
Faulting package full name: 
Faulting package-relative application ID: 

ig8icd64.dll is OpenGL driver for Intel graphics accelerator.

Apparently the problem is in the driver for the integrated graphics. I checked, I have the latest driver version, tried rolling back the driver version, checked 5 versions, but nothing helped.

Apparently it's the old integrated graphics that are the problem.

Everything works fine on Linux, on the same hardware.

[iseos]

In general, I ruled out hardware failure in the computer, conducted diagnostics at a service center, and the device is in good condition. I also tried it on a clean Windows 10 system; however, the error persists.

Ultimately, the issue seems to lie with the driver, most likely. As far as I understand, the error code 0xc0000005 is related to memory; the application can't read a region in the RAM or access is blocked. But I might be mistaken, as I'm not well-versed in this topic.

Could you perhaps recommend what else can be done to identify what exactly is causing this problem? Or maybe suggest reaching out to Intel or the device manufacturer?

It's possible that with the release of DirectX support, this issue might cease to appear for me...

[Calinou]

Or maybe suggest reaching out to Intel or the device manufacturer?

Intel will just tell you to buy a newer system 🙂
Since 2023, they don't provide any support for IGPs older than Tiger Lake (2020). Their support period is the shortest by far, even shorter than AMD.

It's possible that with the release of DirectX support, this issue might cease to appear for me...

Old Intel IGPs probably don't have Direct3D 12 support with the feature level required by #70315 though. (The feature level required is comparable to the one supported by Kepler and GCN 2.0 GPUs.)

[iseos]

Trouble in general :)
It seems that I'll have to explore alternative solutions to the issue, possibly considering changing the operating system or upgrading the hardware.
Thank you for paying attention to this problem, I'm truly grateful.

[iseos]

The workaround for now is to disable multi-window mode:
Go to editor settings -> Interface -> Editor -> Single Window Mode: On
Then (optional) Interface -> Multi Window -> Enable: Off

I think issue can be closed, the engine side is unlikely to fix it, the driver side will definitely not fix it. The only true solution would be to update the hardware.

[Calinou]

I think issue can be closed, the engine side is unlikely to fix it, the driver side will definitely not fix it. The only true solution would be to update the hardware.

I think we should at least work around the issue by forcing single-window mode on those old Intel IGPs, so that the crash is harder to run into by unsuspecting users.

[iseos]

With the use of OpenGL ANGLE the problem disappeared, but more tests are needed.