godotengine / godotengine/godot

Manually closing a window during a breakpoint leaves a white screen behind

Open
#91,256 1 comment 0 reactions 0 assignees View on GitHub
bug topic:platforms topic:rendering
Dominant language
C++
Stars
117k
Forks
26.8k
PR merge metrics
PR metrics pending

Description

### Tested versions

Godot v4.2.2.stable
Godot v4.2.1.stable

### System information

Windows 10.0.19045 - GLES3 (Compatibility) - AMD Radeon RX 5700 XT () - AMD Ryzen 5 3600 6-Core Processor (12 Threads)

### Issue description

If you manually close a game window using the windows titlebar while it's frozen due to a breakpoint, it will leave behind a white artifact that cannot be closed, moved, or interacted with in any way I'm aware of.

![image](https://github.com/godotengine/godot/assets/87352493/e957b851-bf1f-42c9-a0ac-695160244995)

Additional Notes:
This bug includes all windows opened by the game, and all windows maintain some flags. If a window has always_on_top checked, it's remaining artifact will be always on top.

The only way I've found to get rid of these windows is to restart my computer, or to replicate the bug and produce a new artifact, which seems to remove the previous artifacts

### Steps to reproduce

- Create an empty project
- Create any scene
- Add a script to the scene, and put any code in the "_ready" function.
- Add a breakpoint to this code, so the window will enter a breakpoint when run
- During the breakpoint, close the window using the windows close button found in the windows title bar. Using task manager does not reproduce this bug.

### Minimal reproduction project (MRP)

N/A

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue in the empty project on Windows, using the breakpoint and title-bar close steps described above. Trace the Windows window-management and breakpoint/debugger paths involved in closing the game window; done means no unresponsive white artifact remains, including for additional or always-on-top windows.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop, game-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.