How Do I Fix the VRAM Leak (Don't Tell Me There Isn't One, I've Seen it in My Tests)

[VeterN]

I want to start out by saying this game is extremely fun! The gameplay is unique and well designed. The objectives, checkpoints, equipment, shark upgrades, etc. are all enjoyable.

But here is the issue I've been experiencing, and I've seen it first hand in the tests I ran.

This game has a VRAM leak, and I'm not sure where this bug exists so I can adjust to correct the issue. I've seen no help on the matter in any forums. The game will crash and then display a window stating it's closing due to running out of VRAM. My graphics card should never run out of VRAM on this game, so this brought up concern with the leak. Is there a Steam Launch Preference I can input (i.e. " - VRAM Limit 11000mb")?

My specs:
i7 8700k on water
Asus Poseidon 1080 ti (***11Gb VRAM***)
16Gb 3000mhz RAM
The game is on a 1Tb M.2 SSD

[VeterN]

It happens every other match for me. There is in fact a VRAM leak. Run simple tests and you'll see it, other than letting it just happen and restart. I'm not just some gamer that doesn't know what I'm talking about. When a window opens up stating the game ran out of VRAM it's usually an indicator.

Most common issue results form a bug within a graphics setting itself, rather than how high your settings are.

[SeanXD]

There Isn't One

[Snake [日本あアｱＡ]]

Can you tell us more about your PC? What OS are you on? What driver revision are you on?

It is entirely possible we have a Vram leak but we are in 32 bit land, so addressing all of your Vram isn't possible. More likely we are running out due to that...

[VeterN]

@Snake Wow, thank you for caring and your support. Many discussions go unsupported by a developer, and I thank you for taking your time to come by.

I am on Windows 10 Pro 64 bit. Currently up to date on Windows updates, AND Nvidia drivers, driver 441.87. I haven't done any manual overclocking of this system, I have only enabled the XMP Profile and allowed the CPU to Turbo. RAM is at its rated 3000mhz, no overclocking there. Same goes for the GPU, I just have it set to its rated OC Mode default to the cards bios.

I only have applications like Discord running, but that affects system RAM, not VRAM. If it's in 32 bit, and it won't allow access to the full amount of VRAM capable with my card, then what is there for me to do?

[VeterN]

It's unplayable for me... It crashes every match. I hope we can get a resolution to this issue, and I'm more than willing to put the resolution out there, it may help someone else.

[DefectiveByDesign]

Messaggio originale di Snake:

It is entirely possible we have a Vram leak but we are in 32 bit land, so addressing all of your Vram isn't possible. More likely we are running out due to that...

It's likely to be a driver/api related memory leak due to having abnormally large Vram, which is outside of mainstream configurations. Nvidia probably overlooked it.
https://en.wikipedia.org/wiki/3_GB_barrier
You need PAE and memory hole remapping workarounds to deal with 32-bit applications, and there were many driver problems in 32-bit land when ram started reaching past 4GB. Creative soundcard drivers were broken for a good while due to this. Anyone gaming on hardware having over 8GB Vram is outside the norm, and the bug was most likely overlooked due to lack of testing. It could exist anywhere between the game, OS, or driver.

If this bug is due to having too much Vram, you have two options.
1: Bug report to Nvidia.
2: Manually execute the 64-bit Depth exe in the game folder outside of steam.

If you still have the memory leak using the 64-bit exe, then the leak is more likely with the game, while if not, the leak is with the drivers and must be fixed by nvidia.

This is going to be a much bigger problem moving forward, as video cards keep increasing Vram. It will be better to update the game, than duct tape over 32-bit bugs while praying the whole thing doesn't suddenly break and cause players to quit.

[VeterN]

Thank you, when I'm online next I'll test executing the 64 bit and update the discussion.