Control DXR possible memory leak

[screwylightbulb]

Super hard to replicate. I got an out of video memory error crash 2 times yesterday while using DXR. Happened today too, but I was playing over an hour before it happened. Nothing useful in the log, and looking at the graph, it's not like a massive spike or anything.

Actually it may be related to shader compilation, because it crashed today as I was entering a different area.

I am on:
Kernel 5.10
Nvidia driver 460.56
RTX3060Ti

Proton 5.13-6

[doitsujin]

what does "out of video memory error crash" mean exactly? Is that a message from the game itself or from the vkd3d log?

vkd3d itself generally cannot really leak video memory; allocating and freeing VRAM is the application's job in D3D12. Control is known to make lots and lots and lots of very small allocations though which may cause fragmentation and increase usage over what you see on a native D3D12 driver.

In my experience, the 6GB on my mobile RTX 2060 isn't enough to run this game adequately with DXR at 1080p or 1440p even on Windows, so the 8GB on your card might just not be enough given that Nvidia's Linux driver also has more limitations regarding memory allocation. However, if we fail to allocate memory, it should show up in the logs, provided you have that enabled.

[screwylightbulb]

This is from the game itself. A crash notification pops up with a message that says it is out of video ram. The log did not have anything in it worth mentioning. I could try upping the log level.

[HansKristian-Work]

If it's shader compilation, I expect you'd get a crash when entering a specific area or something where the game needs some specific RT shaders or something we haven't seen yet.

[screwylightbulb]

If it's shader compilation, I expect you'd get a crash when entering a specific area or something where the game needs some specific RT shaders or something we haven't seen yet.

Yeah, today it crashed with this while entering a new area. The 2 times it crashed yesterday was a different area, and it did not crash in that area today at all.

[iddm]

What is your resolution? I couldn't run 4K at all with ray tracing enabled with my 10gb videocard, but on windows with dlss from 1440p it ran just fine (understandable why).

So on Linux, 4K with ray tracing - the game crashes. But actually quite fast, I don't have to wait long.

[screwylightbulb]

What is your resolution?

1440. I could try with 1080.

[iddm]

What is your resolution?

1440. I could try with 1080.

I started the full game from the beginning and have finished it fully with ray tracing on Linux at 1080p, with no crashes whatsoever, so I guess is that you just run out of memory because you have a fairly low ram capacity on your video card for these games at more or less high resolution including all these effects.

[Blisto91]

@screwylightbulb Friendly ping and a hello 👋
Do you still experience this issue?

[HansKristian-Work]

Assuming to be fixed, and no activity in a year.

[syberphunk]

I believe I've experienced this issue @Blisto91 / @HansKristian-Work

Here's a log file:
steam-heroic-Control.log

Which has messages of:
648.573:01b4:0214:warn:vkd3d-proton:vkd3d_allocate_device_memory: Memory allocation failed, falling back to system memory.

And a video demonstrating how it behaves when it happens:
https://youtu.be/2M40O7ODzJ4