I do not know what that feature is,
DXR is ray tracing. Although given that there are no other reports about CP77 leaking memory by default, I'm inclined to blame Intel's vulkan driver here.
I'm inclined to blame Intel's vulkan driver here.
Wouldn't be very surprising.
Though regardless of the blame the issue was tedious to narrow down, I imagine less technical users would give up.
I hope there would be something to remedy it.
Does disabling DXR cause issues with ray tracing features, aside from them maybe not working?
I would add a note on ProtonDB about it.
Does disabling DXR cause issues with ray tracing features, aside from them maybe not working?
Ray tracing features will definitely stop working if you disable dxr. Some games might gate some other technically unrelated features behind dxr being supported, though I don't know if CP77 is one of them, sounds like it isn't. You can report driver bugs here: https://gitlab.freedesktop.org/mesa/mesa/-/issues
@l-t-s I was experiencing the same issue with my B580, but on Steam instead of GOG, so thanks for the workaround! Did you end up creating an issue on the Mesa GitLab page?
@l-t-s I was experiencing the same issue with my B580, but on Steam instead of GOG, so thanks for the workaround! Did you end up creating an issue on the Mesa GitLab page?
Oh apologies! I got conveniently busy around the time and forgot about the whole thing, so I have not made any Mesa issue. I'll look if there is something I can do, if no other issue has been brought up yet.
And thank you for responding as well! I wasn't sure if anyone using Steam was affected at first since I couldn't really find other issues about this.
I have found https://gitlab.freedesktop.org/mesa/mesa/-/issues/12458 which may be related, no mention of DXR but it seems to be something related to ray tracing.
Multiple people have ran into this with MSI-Claw hardware running ReignOS.
It also is easy to reproduce using Rise of the Tomb Raider using D3D12 mode (doesn't happen in D3D11 mode)
I think this might be a Intel Mesa issue more than a Proton issue but IDK.
VKD3D_CONFIG=nodxr`,x1 2025-07
I found that by setting
VKD3D_CONFIG=nodxr, Cyberpunk would no longer consume all of system memory and hang the thread on close.I was attempting to play Cyberpunk 2077, which I had bought from GOG, via Lutris. Starting the game worked fine and remained relatively stable for a few minutes. A moment later the game would freeze and my whole system with it, until the OOM killer would kick in to start shooting down whatever processes I had open.
I observed the game's resource usage and saw it would immediately jump to around 6GB RAM usage on the intro, slowly increasing to around 8GB in the main menu, and finally when loading into a save it would be around 10GB from where it would over time increase to fill my full 32GB RAM and 16GB pagefile, freezing the system and activating the OOM killer.
So I tried a variety of things: different kernels (zen, lts, cachyos), GE-Proton and Wine versions available on Lutris, (de)activating some additional features and changing game settings.
None of those had an effect and the result was the same. I later faced the same issue on HeroicLauncher.
Eventually I tried different versions of the Lutris runner libraries for Wine, and I found VKD3D 2.10 ran perfectly fine; Cyberpunk launched to around 2GB RAM usage, climbed to 4GB loading into a save, and hovered well under 6GB for hours without issue.
Checking the release notes for VKD3D 2.11 I saw that DXR became the default option, so I disabled it with the
nodxroption, and it worked.I do not know what that feature is, what it is meant to do or why it causes the game to consume all memory and hang the thread, but I'm quite sure the issue stems from its interaction with something on my system.
Software information
Cyberpunk 2077 from GOG, downloaded and managed using Lutris and HeroicLauncher.
On Lutris, with runner being a Wine version, all current default versions for DXVK, VKD3D, D3D Extras and DXVK-NVAPI.
Medium settings in-game with raytracing, upscaling and frame generation turned off.
System information
Log files
Proton created 2 log files, the other with a lot of output, so I archived them.
dxr_ge-proton-10.10_logs.tar.gz
This first is with DXR enabled, few minutes in-game, and having to SIGKILL the process after quitting.
nodxr_ge-proton-10.10_logs.tar.gz
With DXR disabled, roughly same sequence as first, game closes normally.