Vulkan: Huge memory usage and performance drop after resizing the game window

[marcinn]

Godot version

v4.0.alpha.custom_build.eb6ebdc4a

System information

Manjaro Linux, 5.10.105-1-MANJARO, x86_64, NVIDIA GM107GLM [Quadro M620 Mobile] nvidia 510.54, X11, Vulkan

Issue description

After resizing the game window, fps are dropped by about half. Also there is noticeable huge memory usage, which also looks like a memory leak. And when you resize the window few times more, you should hang your OS due to out of memory.

https://www.youtube.com/watch?v=Xd9wGFQBbzk

The issue exists both on X11 and Gnome/Wayland.

Steps to reproduce

1. Open the project and run the main scene
2. Make window way smaller. You should notice a huge lag and increased memory usage.
3. Then the memory usage will drop almost to original value, but it will be slightly greater. Performance will be dropped about half (check fps)
4. Resize the window few times more in a short time. Your PC will hang due to OOM.

Minimal reproduction project

Should be any project, but I'm attaching the one used to record the video.
PopupCrash.zip

[Calinou]

Related to #56205.

In general, changing graphics settings can cause various resource leaks, which you can test by using https://github.com/Calinou/godot-photo-mode-demo.

[avilches]

I do confirm this is happening in Godot 4 beta 6 too. FPS drops from 60 to 20, 6... 1 after resizing window some times, tested in a ported game from Godot 3.0. (It's a 2D game, no fog)

[darksylinc]

Is this still an issue? I cannot reproduce this issue on Xubuntu 20.04 with Godot 4.2 master on AMD GPUs.

Neither the memory leak nor the performance degradation. However the perf degradation could be NVIDIA specific.

I noticed this triggers a pathological case of #80570 which will be fixed when #80571 gets merged.

Thus perhaps after merging that PR the slowdown will be gone?

[Calinou]

https://github.com/Calinou/godot-photo-mode-demo in 4.2.dev3 on a NVIDIA GeForce RTX 4090 exhibits permanently increased VRAM usage after settings are temporarily increased once (from 3.8 GB to 5.3 GB), and then twice (from 5.3 GB to 5.5 GB). Subsequent settings toggles don't affect VRAM usage significantly:

simplescreenrecorder-2023-08-14_14.50.41.mp4

However, if I perform the same operation in 4K, a permanent performance drop occurs after VRAM is fully exhausted by the settings toggle. (This photo mode internally renders the viewport in 8K if the window size is 4K.)

simplescreenrecorder-2023-08-14_14.52.34.mp4

VRAM exhaustion is supposed to destroy performance, but I think performance should go back to normal levels after VRAM usage goes to normal levels and previous settings are restored.

Edit: Moved to #81258.

[lostminds]

Regarding the memory leak when resizing the window, could that be the same as #77295 ? Still an issue on 4.2.dev3 now that I tried it.
Seems like it's allocating a large number of new buffers of some sort for the new size during window resize that aren't properly released as the window keeps changing size and new resources are allocated for the new size.