Pretty bad memory leak issues?

[Tony Salami]

Just as the title claims (or could be something entirely else). Can play for about 1h (sometimes way more, sometimes way less) with absolutely no problems and rock solid 60. After that it always gets worse and worse, down to low 40s. A restart of the game always fixes the issues. Hope they fix, as I want to play this lovely game as much as possible :)

[Dr. Pizza]

Yeah I got this too. 32 GB RAM, on same NVME drive as you. After some playtime I get some fps drops and mem usage increases up to 25GB or more and then it crashes

[HAPPY BIRTHDAY PAULIE]

Had it happen once to me so far. RAM usage went up to 40GB and then game stopped responding. GOG version.

Updated drivers,

64GB ddr4
i5 12600k
RTX 4090

[Shosen]

I have this issue as wel. My frames will drop from 60 to 30/20 after an hour'ish of gamrplay, and only restarting the game fixes this. I've noticed that using the photomode or pausing the game frequantly in a row speeds up the problem.

[GingerWitch]

Memory leak would effect everyone. I play for hours at a time (5+). I've had 2 crashes in 35 hours game time since 2.0. I have less memory in my PC than other people with this problem.

[Aragashia]

I've experienced something akin to memory leaks a lot since the 2.0 patch where it'll (after playing for a while, opening and closing stuff) slow down to a crawl and then won't recover until a restart. It's very similar to the old map/inventory issue in my case, and sometimes quickly opening/closing the menu "resets" it temporarily. I've never crashed due to this, just slowed down to about 5-15 FPS.

Looked all over the place for a solution, because the game runs well until this happens, despite my poor choice of using a 4k monitor (locked at 57 FPS on a 4K 60hz monitor with DLSS Balanced, PT, RR and FG enabled).

I ended up finding that (in my case) lowering texture quality to medium as a temporary solution resolved the issue, and it hasn't happened at all since then. I'm not knowledgeable enough to tell you the root cause though.

Windows 10
AMD Ryzen 7 5800X
RTX 4070 Ti 12GB
16B DDR4 3200MHz
Samsung SSD 980 PRO 1TB

[❀❀ V ❀❀]

Wintermist님이 먼저 게시:

var님이 먼저 게시:

its an NVIDIA issue related to Ray Tracing and 8GB cards that nvidia doesnt care about fixing because it pushes their users to spend more money on their bigger cards. it was reported way back in 2020 to radio silence. the caching npcs issue in cyberpunk exacerbates it a bit but basically Ray Tracing and DLSS end up pushing toward the 7.5GB limit on their own so the games themselves start to run out of allocatable video memory after about an hour or two. this is why you can fix it with a save and load at first but eventually thats not going to work either and you will need to restart. this issue also appears in Doom Eternal when you turn Ray Tracing on.

you can see for yourself by disabling Ray Tracing and seeing that magically the game never has the same kind of performance degredation. sometimes itll fix it right there without a restart.

Hmm yeah, turns out lowering textures didn't help. You're right in that turning off Raytracing altogether is the solution, this is a bummer. It looks so much nicer with it on, but if I can't play with it on then what's the point.

3070
10700K

Yep. CDPR will probably find a workaround again but the issue will always have a way to present itself until NVIDIA does something about their current RT implementation. I also shouldn't have said 8GB cards as it can happen to all cards, 8GB cards are just the most susceptible as theyll reach the limit much quicker. NVIDIA needs to stop skimping out on VRAM and acting like its a premium feature and not an absolute necessity.
https://www.reddit.com/r/nvidia/comments/10n4ea7/the_memory_leak_dilemma_is_rt_implementation/

GingerWitch님이 먼저 게시:

Memory leak would effect everyone. I play for hours at a time (5+). I've had 2 crashes in 35 hours game time since 2.0. I have less memory in my PC than other people with this problem.

This particular issue only causes a crash when you go back to the main menu. It does not cause a crash during gameplay as it starts swapping system RAM which is why the game starts to chug. You would only crash if you then also ran out of system memory. It's also almost exclusively an NVIDIA GPU issue.

[cdshivers]

Wanted to chime in chooms... I've got a high end rig and also have this issue (specs below). For reference I run the game at MAX settings. I have multiple 4K texture packs, increased LOD mods and just about anything I could find to make this beautiful game look even better. Now I know what y'all are thinking "Well of course you'd have performance issues with those mods and max settings...". Thing is, I'd agree with you if I didn't have my rig.

That said, I run the game at 4K DLSS Quality, (but now balanced mode since this bug is an issue). RT/PT on, again everything maxed. When I first load the game, I'll get a buttery smooth, 88-96 FPS. Once I either open the map (which is usually my trigger or vendor menus) or play for a little while, I will drop to the 45-55 FPS range. I can literally quick save when the FPS drops, load that save and gain at least an additional 30+ FPS.

Sure I could turn off RT/PT, but that's not why I play Cyberpunk. I love the visuals and my rig (regardless of my mods) should and does run this game at a high frame rate. Well initially anyway... lol.

Just wanted to put that out there so a bunch of you can put to rest it being just mid-range to lower end hardware. As of this post, I also just updated my video drivers and still have the same issue.

::SPECS::
4090 Founders Edition Water cooled (EKWB water block)
Intel i9 13900K also Water cooled (EKWB water block)
Game installed on NVME M.2 Samsung 990 Pro 2TB (same as OS)
Windows 11
Corsair 32GB Ram on stock 7200mhz clock
Asus Z790 Extreme MB (using the built in overclock from the MB, VMP I think is what it's called)