SexArcana
SexArcana
About
- Username
- SexArcana
- Joined
- Visits
- 60
- Last Active
Comments
-
This can be closed as a Technical Issue now, but I'd wait until the next release of mesa when it "officially" gets fixed since not everybody has the ability to use source packages. It was a mesa bug as I suspected in the last post.
System information System: Host:...For anyone else experiencing the issue, switch to mesa-git for the time being until it's pushed to upstream. It'll pull in the commits to RADV that fix the DBD shader leak. AMDVLK users, uh, tough luck I guess.
-
Yeah this appears to be a very specific bug targeting Radeon systems. Weird thing was that the game was working just fine until around midnight the 23rd. As I've said it's not a driver or kernel issue, I've tried rolling back both to no avail.
The only package that I haven't checked is mesa (which I upgraded on the 22nd) but I don't want to risk rolling back all of its dependencies and permanently ruining my install. Besides that mesa already has really tight version control because of how important it is as a core package, so it's unlikely to be the issue.
If I could read my own logs for the game I could probably narrow down where the issue is coming from but unfortunately we're just gonna have to wait for BHVR to do it.
-
Update: Bug appears to be exclusive to AMD processors/gpus. After attempting to reproduce the bug again on my gentoo machine I found that the crash happened for a completely different reason entirely (being that my installation was horrifically misconfigured and EVERYTHING on the system was using extremely high resources). Attempting to reproduce it with a properly configured install was impossible. Bug still stands as-is on the ROG and the Deck, both of which use AMD Renoir.
I'd also like to note that I've tried downgrading the kernel and installing alternative blobs for the drivers, and it's gotten me nowhere. The game still leaks even on extremely old kernel versions as well. Either this is a breaking change in a very specific wine dependency (which would be documented) or a game bug, and I'm heavily inclined to believe it's the latter.
-
I personally don't really like looping, I prefer being able to make high investment plays where I can immediately disappear, and that's what I make my build around most of the time. I'd like to see a new way to throw off the killer in a chase other than blinding/stunning, which is part of why I really like Chemical Trap in the PTB. Chase escapes are far more enjoyable when you have more going into them than just running away for 20 minutes.
-
I'm having a separate issue where the game itself actually fills memory on a few of my systems, not the steamwebhelper process. From what I know the steamwebhelper thing is a known issue in steam caused by a large number of factors including the overlay and client library that used to be fixable with the --no-browser flag which valve decided to remove. I've heard it can be alleviated by disabling the overlay or in worst case reinstalling steam or switching to a different vulkan driver such as RADV instead of AMDVLK.
My issue is a bit different, in that the game process itself is taking up resources, under a similar situation; it only starts leaking once I get to the campfire screen. I haven't found any solution to it yet since it appears to be a bug, and I've already made a ticket for it.
-
Em ingles, por favor.
Informacao de error em portuguesa esta https://forums.bhvr.com/dead-by-daylight/categories/bug-reports-pt.
Side note: I am no longer able to recognize Portuguese from Spanish. My avo is probably crying.
-
I'm having the same issue on Arch, the game hangs after around 8GB eats up over 12GB of Memory before earlyoom eventually kills it.
I've tried multiple different versions of Proton, running the game with and without a predownloaded shader cache, nothing does anything. I get to campfire and after around 20-30 seconds it eats up the maximum available memory on my PC if I disable earlyoom.
To note: I'm running an AMD Ryzen+Radeon system using Arch Linux kernel 6.4.11-arch2-1 on KDE Plasma X11, running the game under my package maintainer's version of Steam (steam-runtime). It's not a driver issue, I've tried both lib32-vulkan-radeon (mesa) and lib32-amdvlk (amd open) and the memory leak happens with both. I haven't tried lib32-vulkan-amdgpu-pro (amd proprietary) because it's just actively worse than the other two.
I'd also like to note that this only started happening today, out of the blue. I didn't even update any packages, it just sponrtaneously started leaking memory.