Not sure where to post this, thought this might be a good starting point. My system specs/configuration:

OS: NixOS 24.05.20240323.44d0940 (Uakari) x86_64

Host: ASUSTeK COMPUTER INC. WS C246 PRO

Kernel: 6.6.22

Resolution: 2560x1440 (60 Hz), 2560x1440 (165 Hz)

DE: Hyprland (Wayland)

CPU: Intel i9-9900K (16) @ 5.000GHz

GPU: NVIDIA GeForce RTX 4080 SUPER

Memory: 4845MiB / 15858MiB

So sometimes, when I'm playing BG3, it will completely freeze my system. I'll just be playing regularly, and then suddenly it starts to grind to a halt quite quickly. In my mangohud, I'll see the frame times go to 850ms, it will play a few more frames, and play the audio in very short, chopped up parts. My system will turn completely turn unusable at this point. I think that for instance hotkeys will register but be handled as soon as the system is no longer locked up.

Coming to that, the system will continue after about 20 minutes (not every time, usually I would just press the reset button on my case so I don't have many data points of this, last time it happened I went for a walk and when I came back my system was back "online"), after which I can just continue to use the system normally, though both steam AND bg3 will have crashed (I can just restart them no problem though).

I'm currently playing it through Proton-GE-9.4, but I've also played on Proton-Experimental and Proton-8.0. I'm launching with these options (just copied from ProtonDB from someone with nvidia GPU with a similar generation one):

env --unset SDL_VIDEODRIVER PROTON_ENABLE_NVAPI=1 DXVK_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr,dxr11 PROTON_HIDE_NVIDIA_GPU=0 mangohud %command% --skip-launcher --vulkan

Vulkan or DXVK makes no difference either. I do not run into this with any other games, cyberpunk 2077, for instance, runs fine all the time.

From the logs it looks like some process either has a memory leak or just goes completely rogue with memory usage.

In my journalctl, a lot of logs occur (what stands out to me is the discord app blocking, I will now try to play without discord turned on, see what that does). System seems to recover after about 20 minutes (wasn't there to see though). Not sure how I can best show the log, because it's about a thousand lines spewed out in a quite short time.