32Gb ram is not enough..

[Ronkvistarn]

After some time ~2 hours of playing my ram memory goes finito.. stalker has eaten up all of it and crashes. I wonder..
-Is it me who´s cheap and need to buy another 32gb?
-Is it bad optimizing?
-Is it just what it is, deal with it and buy moar ram (or download) more ram from internet downloadmoarram.haxx.c*m

[thestile]

I don't think I've had a memory leak since Ark Survival Evolved.
That must be one for sure.

[atrox]

Well, strangely I'm coming close to 200h in game and never had memory issues with 32GB ram. Of course the usual MEM_ACCESS_VIOLATION crashes, but that is bad programming using invalid pointers.

Of course there may be mem leaks, but I doubt it with modern environments. UE engine mem consumption is usually fine, it's written with crappy consoles in mind.

What really eats up memory and usually has mem leaks:
* Browsers. A single browser tab likes to use 1G ram nowadays, no joke.
* social media apps, badly written or using up resources spying/scannig you
* video players that aggressielvy cache or hold media in memory

So close them, and disable autostart of them.

The only real Stalker related mem issue experienced is with mods that were outdated.

[seven_stars]

atrox님이 먼저 게시:

Well, strangely I'm coming close to 200h in game and never had memory issues with 32GB ram. Of course the usual MEM_ACCESS_VIOLATION crashes, but that is bad programming using invalid pointers.

Of course there may be mem leaks, but I doubt it with modern environments. UE engine mem consumption is usually fine, it's written with crappy consoles in mind.

What really eats up memory and usually has mem leaks:
* Browsers. A single browser tab likes to use 1G ram nowadays, no joke.
* social media apps, badly written or using up resources spying/scannig you
* video players that aggressielvy cache or hold media in memory

So close them, and disable autostart of them.

The only real Stalker related mem issue experienced is with mods that were outdated.

Then why with 200h in game the issue for me and tons of others is only in Rostock?

[atrox]

seven_stars님이 먼저 게시:

Then why with 200h in game the issue for me and tons of others is only in Rostock?

Uhm, question other way around - why is it not hitting me?

No offense, I may be doing something different somehow, not triggering it.

(The only special thing I know of Rostok is the red weapons trader. I never carry red weapons or sell them.)

[seven_stars]

atrox님이 먼저 게시:

seven_stars님이 먼저 게시:

Then why with 200h in game the issue for me and tons of others is only in Rostock?

Uhm, question other way around - why not me? No offense, I may be doing something different somehow.

Something is different.
My setup
I9 13900HX
32gb ddr5
Samsung 990pro drive
Rtx 4080
Windows 11
External monitor game set to 1440p

All settings at epic

[atrox]

Older comp with recent graphics and real fast storage:
Intel i7 5960x OC@4.3Ghz
32gb ddr4
Win 10
all drives SSD
RTX 4070
Philips 4k display

Running full 4k@60hz high settings

Edit: It may be the full 8 cores (and not the defective i9 E ones), older Win10.

Edit 2: But as said I doubt it. Mem leaks are seldom with modern programming environments unless you really force them or don't know what you are doing. You already get warnings at compile time, using modern code validators/checkers nearly eliminate them.
There is usually an other mem hogger mentioned above.

[GypsyDogZ]

apparently Unreal Engine 5 is the issue with all current games on it. Lazy editing and skins. But im running 64gb on 4 sticks at 5600mhz . I do see it using 28GB, and my rx 7800 xt oc is using 10-11gb on epic settings. I also am using a undervolted i7-14700k at 5.7ghz Pcores and 4.4GHZ Ecores set to max (1.433 volts) max spike temp 74oC, max gpu temp hot spot 71oC

[StrangestEcho]

atrox님이 먼저 게시:

Edit 2: But as said I doubt it. Mem leaks are seldom with modern programming environments unless you really force them or don't know what you are doing. You already get warnings at compile time, using modern code validators/checkers nearly eliminate them.
There is usually an other mem hogger mentioned above.

I have 64gb of memory and a 4090. I'll see Stalker 2 hit around 54GB of memory utilization and then lock up while in Rostok. It's a ♥♥♥♥♥♥♥ memory leak.

[Martin]

Is the Frame Gen enabled bug still a thing for RAM leaks? I read a few times that FG was the potential cause.

I have a 7900 X3D CPU
32GB DDR5 6000
RTX 4080

All EPIC settings apart from DoF low
4K with DLSS quality
Frame Gen turned OFF.

In over 200 hours I have had no performance issues (other than Faust fight) and only a few crashes. More pertinently I have never had a memory leak running this game. That includes using Rostock as a trade hub for large portions of the game.

[[K]entucky Sperkle ♿]

alot of non Rostok-Certified pc's in here

[BRT Cobra]

it should be noted that nvidia overlay is causing memory issues.
was the first thing i disabled for this game. maybe that is your issue?

[impactos_enredos0i]

Kentucky Sperkle ♿님이 먼저 게시:

alot of non Rostok-Certified pc's in here

:Emil:

[OldWhiteWolf71]

If you find ANY game using UE5 crashes semi-randomly, use your motherboard manufacturer's app for overclocking to REDUCE the CPU multiplier until it runs normally.

With my old processor (Intel) rated at 54x100 I had to drop it down to 48x100 for the UE5 engine to run properly. Entirely Intel's fault for releasing poorly made CPUs.

[Greymantle]

No Freezing until the last patch. I don't have to be in Rostock for the memory leak issue. I horde everything so maybe I need to stop doing that. sigh

[Nite69]

I'm playing on 16GB its only the main bases I have problems with sometimes but when out exploring and doing missions its fine