Memory Leak Bug?

[LuceroArts]

So I seem to have found an issue where at the start of the game after the introductory cutscenes. The in-engine cutscene in the dive into the heart area appears to progressively consume a very large amount of memory in system ram and vram. On my system I've seen it consume 24 GB of vram and up to 45 GB of system ram. It appears to occur due to the unlocked fps cap and 120 fps cap setting. Setting the cap to 60 fixes this issue. I've also tested this at 1080p and 4K resolution with uncapped fps and the issue will occur on either resolutions. The game does recover at the end of the cutscene, but I'm pretty sure users with less memory will crash. Not sure if this is an Nvidia driver bug or the game, but no other game I've played has this issue. Even though this issue recovers I wouldn't be surprised if this issue occurs in other cutscenes or areas in the game.

Edit: Sometimes the issue fails to occur when the fps cap is set 120 FPS and when Vsync is set to on.

Video of the Issue: https://youtu.be/L3Q2mOBiQQE?si=e4lC6NJdC2oVW6Cl

My System Specs:
CPU: AMD Ryzen 9 7950x3D
Ram: 64 GB 6000 MHz C30 Expo set to on.
GPU: RTX 3090 Founders Edition set to Stock
Storage: The game is installed on a Samsung 970 Evo
Nvidia Driver: 555.99

[RiGoRmOrTiS]

yes this is the issue lots of people have; I've found if you pause the game and wait 10 seconds or so, it will fix the issue for a while until a future random in-engine cut scene causes it to happen again. if you don't do it. you are right. it gobbles up VRAM until it crashes. I had it gobble up all 24GB of my 4090 and then crash.

[HippeusOmega]

I've had this happen to me also today. Where it devoured almost all 32gb of system memory and my 3080ti.

I have noticed I've been able to reproduce it with the rendering scaling at anything higher then 100% with engine cutscenes.

[Gaz]

I posted this a few days ago as i was having similar issues since launch on EGS and was wondering if the issues were fixed for the Steam version
https://steamcommunity.com/app/2552450/discussions/0/6234751259568021217/
I guess they arent and seeing as this has not been patched in 3 years i wouldnt hold my breath for the steam version either.

[libretro]

Ran into this recently too. I kept doing tests wondering what was up. Then ran across this thread. Very disappointing to hear this is a memory leak at framerates > 60fps. Pretty much makes it a 60fps locked game if you want a crash free experience.

Was running it at 3840x2160 with unlocked FPS with a 5090 (so 32GB VRAM). Started dropping down to like 20/10fps at the first boss in the skies. Later tried running it at 120fps locked, instead of dropping to 20/10fps it instead crashes. I guess I should try 60fps locked next and that should be the only thing that manages to run and not OOM.

I really was wondering what was up but now it all makes sense.

Obv a 32GB VRAM card released in 2025 should have more than enough VRAM for a game made for the PS4 and released in 2019, and FPS at this resolution is over 200/300fps so it's obviously the game's fault and is just plainly a memory leak that should have been fixed in an emergency patch years ago.

It's unbelievable how much BS consumers swallow from these AAA publishers really. You really can't be bothered fixing a bug that basically renders your software a broken product for many PCs, really? And this has been going on for years and you don't care to patch it? One of your flagship franchises with Disney backing behind it? Unbelievable really. Don't advertise features in your game if you can't deliver on it and can't even bother patching a memory leak this well known 4 years on. Inexcusably poor showing for Square Enix here.

And then they'll wonder why the next game will inevitably sell below expectations...