PSA: This game has a memory leak.

[Evilnapkin]

If you plan on long sessions and/or changing maps often, close unnecessary background programs (ie. other game platforms) before playing to increase how long you can play before a crash due to running out of memory occurs. If you are above 16gb this will likely take an extremely long session to be an issue for you.

Example: I boot up and I am at 13gb/16gb RAM used on menu. I run the benchmark a few times, then am at 14.7gb/16gb used on menu.

[Diogenes49]

memory leak would explain a lot of the problems now how do we test it? Think GB will give us the source code?

[Tricky]

I never had this problem. playing in window mode while watching something and multitasking. 16gb ram. please stop spreading info that may not apply to EVERYONE.

[Diogenes49]

memory leaks result in problems occurring after playing for a while eventually often resulting in an out of memory error or outright crash in order to troubleshoot it you need the source code It can manifest in a number of ways

[Casurin]

What you described here might not be a memory-leak - increased memory-consumption after running a benchmark-section can just be stored replays and metadata, the compiled sharders, cached textures or whatnot.
If you make such claims at least verify that your claims are correct before posting them, otherwise i might just say "you are a deranged person that wants to kill people".

[MrSnitches]

I personally haven't had this issue.

[Junipercat]

Having 13GB used on boot does seem odd. Though some like to brag that they "personally haven't had this issue.", perhaps we can help find a solution or at least narrow down what about yours results in this memory leak that doesn't affect people across the board (or even the majority).

What are your full computer specs?
Anything else running at same time as game?
Do you have multiple programs overlapping tasks (virus/malware programs, etc.).
Does this issue happen with anything else?
Without using benchmark, just task manager for current use, what is the result in-game?

[Evilnapkin]

It's at 8gb usage when I'm on the starting logos, gets to 13gb by the time I hit the menu. Got to 15.9gb during a boss fight and I thought it was going to crash, but it let me kill the boss and load into the next area.


I close all game launchers before launching BL3, the only game I've had to do this for because of how much memory it uses. Only things running when I play are Epic, Discord, Afterburner, and BL3.

System is

i7 7700k (game doesn't use more than 50% CPU aside from when loading)
16gb RAM
GTX 1070
installed to SSD

Everything but RAM exceeds recommended requirements.

[Evilnapkin]

Originally posted by Casurin:

What you described here might not be a memory-leak - increased memory-consumption after running a benchmark-section can just be stored replays and metadata, the compiled sharders, cached textures or whatnot.

It should be clearing those after they're no longer needed. It doesn't even load the benchmark faster, if the increased RAM usage after running is indeed cached resources it isn't doing anything but hogging memory.

[Diogenes49]

Originally posted by Casurin:

What you described here might not be a memory-leak - increased memory-consumption after running a benchmark-section can just be stored replays and metadata, the compiled sharders, cached textures or whatnot.
If you make such claims at least verify that your claims are correct before posting them, otherwise i might just say "you are a deranged person that wants to kill people".

right stored metadata could be the problem what happens with a memory leak is the program does not erase stored data when it is no longer in use and slowly unused data accumulates give me the source data and I will prove it

[Diogenes49]

Originally posted by Evilnapkin:

Originally posted by Casurin:

What you described here might not be a memory-leak - increased memory-consumption after running a benchmark-section can just be stored replays and metadata, the compiled sharders, cached textures or whatnot.

It should be clearing those after they're no longer needed. It doesn't even load the benchmark faster, if the increased RAM usage after running is indeed cached resources it isn't doing anything but hogging memory.

you hog enough memory and you run out of memory

[Evilnapkin]

I switched to DX11 and the game uses 2.5gb less RAM. Still goes up after having used the benchmark, but I just do that for testing. So DX11 is safer. In a side by side maybe I'd notice a difference but just loading in and running around I'm not going "graphix sux" in comparison.

EDIT: Except performance in DX11 is crap, tons of hitching while speeding around on a map.

EDIT: And it just crashed due to a memory issue when traveling back to the ship, even though I had plenty of RAM and VRAM available.

[MrSnitches]

Originally posted by Junipercat:

Though some like to brag that they "personally haven't had this issue."

How is that statement bragging, what the ♥♥♥♥ are you on about?

I'm not telling him he isn't having the issue, you idiot. I'm saying that I haven't had that issue on MY system in almost 150 hours of playtime.

He's making a blanket statement saying there's a memory leak for everyone as if it's a fact.

[Casurin]

Originally posted by Evilnapkin:

It should be clearing those after they're no longer needed. It doesn't even load the benchmark faster, if the increased RAM usage after running is indeed cached resources it isn't doing anything but hogging memory.

Yes, but sadly this is also rather common.

Originally posted by Diogenes49:

right stored metadata could be the problem what happens with a memory leak is the program does not erase stored data when it is no longer in use and slowly unused data accumulates give me the source data and I will prove it

Memory leak means that there is memory allocated that is no longer reachable, what you describe would just be wasting memory - similar outcome, but very different problem.



To see if there is an actual memory-leak he would need to test to see if there is an actual leak - so testing if there is a repeatable pattern that increases the memory-footprint consistently.
If it is once per level, only a certain number of times or something like that then it would be very likely just some cached data - like metadata, shaders, scores, analytics etc.

[Diogenes49]

https://en.wikipedia.org/wiki/Memory_leak

[Junipercat]

How is that statement bragging,

Someone asks for help. You pop on and say you've personally never had the issue. Since that is not productive in the discussion, certainly doesn't help them find a solution, then it comes off as bragging. Too many others have said similar statements, and then tend to follow it with further statements of "my computer is prefect yours just sucks" or the like.

Intending it as an example of a memory leak that doesn't affect everyone, would have been an earlier perception if you had clarified. Just a little more than saying "it doesn't happen to me" (so why here in the first place then?) would have been helpfull.