Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vulkan renderer not updating screen after computer suspension + memory leak #74094

Closed
ShepDowell opened this issue Feb 28, 2023 · 1 comment
Closed
Labels

Comments

@ShepDowell
Copy link

ShepDowell commented Feb 28, 2023

Godot version

4.0.rc6

System information

Ubuntu 22.10, RTX 2060, Vulkan

Issue description

If I open any Godot 4 project, suspend my computer, then resume it, the renderer no longer updates to the screen. It also causes a memory leak (left it until it hit 4.9 GB). This only occurs when using the Forward+ or Mobility renderer. The Compatibility renderer does not have this issue; it works fine.

It also occurs to exported projects (if Forward+ or Mobility renderer used).

I assume something in the Vulkan renderer is being disconnected by the computer suspension, and is not reconnected when resumed. If I move Godot to a second monitor, then disconnect the monitor, the issue doesn't present, only if I suspend the computer. I cannot test on any other operating system.

Steps to reproduce

  • open any 4.0 project
  • set renderer to Forward+ or Mobility
  • suspend computer
  • resume computer
  • attempt to move or interact with anything in the godot window. Resizing also works

Minimal reproduction project

N/A any project works, including default new project

@ShepDowell ShepDowell changed the title Vulkan renderer not updating screen after computer suspension Vulkan renderer not updating screen after computer suspension + memory leak Feb 28, 2023
@lyuma
Copy link
Contributor

lyuma commented Feb 28, 2023

Duplicate of #52738

@lyuma lyuma marked this as a duplicate of #52738 Feb 28, 2023
@lyuma lyuma closed this as not planned Won't fix, can't repro, duplicate, stale Feb 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants