LS VRAM leak issue

[غسل الشوارع بدماء الكفار ان شاء]

Hi everyone,

Ive noticed an issue with LS where if you keep unscaling and scaling again trying different modes and settings it eventually results in a serious VRAM leak in which the only fix is restarting your PC.

Game: Warhammer 40K darktide
GPU: 7900XTX 24GB
CPU: 7800X3D

Even after losing darktide and LS im in the desktop sitting at 22/24GB vram usage with nothing happening, which massively lowers FPS in any and all games without LS until i restart my PC and the performance with LS on gets worse and worse each time.

I am for some reason not seeing anyone talking about this and id consider it a pretty frustrating issue, been trying different settings but keep needing to restart PC cause of this.

Please look into it.

Thank you

[(ノ°□°)ノ]

Where do you check vram usage?

[Space Detective]

Do you have any specific steps for replicating this? Or is it just "turn upscaling on and off repeatedly, swap between different scaling types and toggle settings on and off as you do so"?

[غسل الشوارع بدماء الكفار ان شاء]

Originally posted by (ノ°□°)ノ:

Where do you check vram usage?

HWinfo64 and adrenalin metrics show massive vram usage, and it make sense to cause games are unplayable until i restart pc

It can be replicated by launching warhammer darktide (id assume any game for that matter, also does it metro exodus enhanced), use X3 mode (tho im very sureit does in X2 aswell), ive been trying to get good settings but unscaling and re scaling causes this huge leak. im on latest adrenalin 20.7 drivers

literally just scaling, get stutters or bad framepacing or maybe didnt do something correctly, unscale, try again, rescale, worse, unscale, re scale, even worse, tried it in both WGC and DXGI. then finally its hideous and serious VRAM leak that requires a pc restart

the reason for this is ive been absolutely struggling to get a good solid performance with LS, since i updated my graphics drivers or windows or LS itself it no longer just doubles the FPS nicely, its wacky and absolutely all over the place with stutters, freezing, poor fps and big base fps drops, prior to me updating anything i'd lock darktide to 72FPS and it would boost to a nice solid 144FPS, tried both WGC and DXGI but DXGI just sucks even more compared to WGC in darktide

but now it dips between 120 and 130 and base fps goes to 40-50 and its just unplayable on the exact same LS settings i used to use. ive tried disablign VRR and freesync to no avail its just really overall s*** performance when it was absolutely perfect, and im not sure if its a windows update, LS update or my gpu driver update causing it, either way something's broken somewhere especially with this VRAM leak.

prior to this i changed nothing, got one day and my same settings on darktide the game was hideous

[Dyna]

Would be great with a resizable bar on off button in widows i guess. The reloading of the hub area was made almost instantly with a recent patch. I am guessing it allocates additional ram above the requirements as the instantly hub reload was a mod earlier.

I think that required 64gb ram and above to work properly. So i hope that gpu is paired with at least 32gb or above.

Darktide is a good game but i would not be surprised if it hit you with a "fun" bug here.

In any case not a LS problem i bet. And i doubt that mod is implemented as standard as they would have to raise the requirements with a 90 days notice.

[غسل الشوارع بدماء الكفار ان شاء]

Resizable bar wont have anything to do with it, its on by default in my bios and ive always had it on, turning it off won't make a difference and even if it does wouldn't be worth it. ive never had it off and LS always worked fine before.

and yea i have 64GB system ram

[غسل الشوارع بدماء الكفار ان شاء]

no it is definitely a lossless scaling problem because it occurs in other games, one such is Metro Exodus Enhanced

[غسل الشوارع بدماء الكفار ان شاء]

LS is simply not releasing VRAM once you end scaling or close the program and the games, requiring a system restart to get it back.

[(ノ°□°)ノ]

When program process terminates, all occupied memory is released by the OS. This applies to all programs, whether there is a memory leak or not, and whether the memory type is RAM or VRAM.

[غسل الشوارع بدماء الكفار ان شاء]

Whatever is supposed to be happening when releasing the memory it simply isn't happening, happens when scaling and unscaling with LS too many times. That certainly is not happeing as it should, after using LS and scaling and unscaling multiple times it is still holding 22GB of my VRAM until I restart the OS, that's it.

[غسل الشوارع بدماء الكفار ان شاء]

Problem as i described above still occurs after terminating LS and the game.

[غسل الشوارع بدماء الكفار ان شاء]

Have also ensured that LS is closed using process lasso and the game, it just doesnt release the memory, its gone till i restart

[(ノ°□°)ノ]

Can you record video demonstating the task manager GPU tab before / after scaling / LS closing?

[Gizzmoe]

Have you tried it with a different GPU driver version?

[Dyna]

Yep need to see a picture of that process usage if no mods in Darktide. And perhaps try lowering worker threads in Darktide settings to something like 10 or 12 instead of 15-16

Know this is not memory related, but i know how the default settings on that game can screw up the performance of a computer with the"default" worker thread settings.

It even put a 64 core CPU on 127 threads.......Fatshark recommended 16 for that. But you only have 16 so go for 12 perhaps.

And cache size is controlled by windows also as it should be i guess. (System)

Maybe try without unlimited shader cache size if enabled also. (GPU)

Only mentioned Rebar because of the ability to use the GPU memory, I would not even consider disabling it either. But it has the capabilities to use the VRAM and should be last on the check list if nothing else works out. I would check that after making sure the PC aint mining crypto heh.

[غسل الشوارع بدماء الكفار ان شاء]

Hey thread can be closed, turns out entire time this was my graphics drivers. A DDU and driver update fixed the problem