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

Godot taking lots of CPU and being unresponsive after suspend on X11 Ubuntu 22.04 #85956

Closed
perry-blueberry opened this issue Dec 9, 2023 · 2 comments

Comments

@perry-blueberry
Copy link

Tested versions

Reproducible in 4.2.0.stable, 4.1.2.stable (and probably all versions since Godot 4.0.stable, including mono versions).

System information

Godot v4.2.stable.mono - Ubuntu 22.04.3 LTS 22.04 - X11 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3070 (nvidia; 535.129.03) - AMD Ryzen 7 3700X 8-Core Processor (16 Threads)

Issue description

After I resume my Ubuntu system from a suspend with Godot previously opened, the Godot editor is unresponsive (if I resize the window for example nothing inside the editor window is redrawn, but the window itself changes size) and it's taking up lots of CPU. Happens every time. Only way to deal with it is to forcibly close the Godot editor.

It seems to have something to with Vulkan as I'm getting these errors thrown continuously:

ERROR: Vulkan: Cannot submit graphics queue. Error code: VK_ERROR_DEVICE_LOST
at: swap_buffers (drivers/vulkan/vulkan_context.cpp:2536)
ERROR: Vulkan: Did not create swapchain successfully. Error code: VK_NOT_READY
at: prepare_buffers (drivers/vulkan/vulkan_context.cpp:2459)

Steps to reproduce

  1. Create a new project in the editor
  2. Suspend Ubuntu without closing editor and project
  3. Awaken Ubuntu to find the error

Minimal reproduction project (MRP)

N/A

@Zireael07
Copy link
Contributor

dupe of #82247

@Calinou
Copy link
Member

Calinou commented Dec 9, 2023

Thanks for the report! Consolidating in #52738. This is a NVIDIA issue we can't fix on our end without large sweeping changes. All other applications using Vulkan on Linux run into the same issue unless they can restart their rendering context entirely in a clean manner (preferably without losing any data).

You may try following the advice on this page at your own risk: https://wiki.archlinux.org/title/NVIDIA/Tips_and_tricks#Preserve_video_memory_after_suspend

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants