Debug error in Exclusive Fullscreen causes game becoming unresponsive, can't alt tab until process is killed/suspended

[Lippanon]

Godot version

v4.0.rc5.official [6296b46]

System information

Windows 10, Vulkan

Issue description

When running a project/game from the editor in Exclusive Fullscreen mode, if an error is thrown, the editor won't be brought to the front/top to show where the error is, like normal. Instead, the project/game process will freeze and become unresponsive and one has to wait for the 'not responding' window to close it, or kill the process.

During this time alt-tab'ing doesn't work for me to go back to the editor (which works fine), I have to Ctrl+alt+del to bring Task Manager with priority (Ctrl+Shift+Esc doesn't work even with Task Manager having 'Always on top' enabled).
This is very annoying when debugging a game in Exclusive Fullscreen mode.

Steps to reproduce

Enable Exclusive Fullscreen (through code or Project Settings) and run into an error.
Run the MRP, it has an error setup on purpose, and has Exclusive Fullscreen enabled.

MRP code:

extends Control

@onready var throw_error = $doesnt_exist

func _ready() -> void:
	print(throw_error.name)

Minimal reproduction project

EF bug.zip

[Calinou]

This should likely be fixed by making the script error handler cause the window to have fullscreen disabled (and maximizing it instead).

[3ter]

This also happens when setting a breakpoint.

The workaround of course is to set the mode in the project settings to something else than Exclusive Fullscreen. is to use the Windows key in case of a Breakpoint or an Error to get back to the editor and see it. Now I don't keep that unstaged change lingering anymore 🙏 .

[Chaosus]

A linked proposal (probably):

• Auto-minimize the full-screen game window when the debugger breaks godot-proposals#6183

[Chaosus]

Should be fixed by

• Fix game window stops responding when debugger pauses #94452