Hello!
OS: Bazzite KDE (Open Nvidia Drivers)
GPU: RTX 4070
CPU: Ryzen 5800X3D
RAM: 24GB
Driver version: 570.86.16 (but tested earlier versions as well)
DE: KDE Plasma 6.2.5 (but happens on Gnome as well)
Display server: Wayland (but happens on X11 as well)
Nvidia bug report sh export:
nvidia-bug-report.tar.gz (399.7 KB)
Me & a couple other users noticed a serve memory leak when playing a native windows game through Wine/Proton (Escape from Tarkov - using Unity 2019.4.39f1) using nvidia’s linux drivers.
We run a modded version that enables dynamic render resolution when aiming down scopes to improve performance.
The mod simply uses built in Unity camera methods to change the render resolution of the main render target when aiming - the scope view will be rendered in full resolution.
AMDGPU + Mesa users report that this issue does not happen for them using the same settings.
The latest windows nvidia drivers also seem to work fine for other users.
Here is a video of the issue (flashing lights warning!):
The VRAM will not free on it’s own after that. The user needs to exit back to the main menu for the VRAM to be freed up.
In the unity log we can see a couple warnings that apparently do not exist when running an AMDGPU / Mesa:
While still loading into the game (probably camera initialization):
[Warning: Unity Log] RenderTexture.Create: Depth|ShadowMap RenderTexture requested without a depth buffer. Changing to a 16 bit depth buffer.
[Warning: Unity Log] RenderTexture.Create: Depth|ShadowMap RenderTexture requested without a depth buffer. Changing to a 16 bit depth buffer.
[Warning: Unity Log] CommandBuffer: temporary render texture not found while executing Windows_BaseOpticCamera(Clone)+00 (Blit destination)
& when pressing the button to aim we see:
[Warning: Unity Log] RenderTexture.Create: Depth|ShadowMap RenderTexture requested without a depth buffer. Changing to a 16 bit depth buffer.
This happens two times, first time on begin zoom (pressing aim button) & on end zoom (releasing aim button), it’s probably recreating the RenderTexture each time.
Also notice the single black frame when beginning to aim. This also does not happen on AMDGPUs using Mesa or on Windows Nvidia drivers.
I’ve tested driver version 565 & settingfbdev=0 as well - same result.
I’ve checked journalctl & the wine logs, but there’s nothing logged when triggering the issue.
There’s also an apitrace available if needed.
Thanks for reading.
(p.s - the lag spikes at the end of the video are the result of all VRAM being used up which might be a nvidia driver or nvidia driver + KDE Plasma 6 issue as well… this can result in the whole desktop environment to crash e.g. when alt-tabbing out. It’s been reported a couple times in the linux beta driver topics ;-) )