Yeah, I spent 4 days testing this. Good thing is, it isn’t really a leak. But it does fill up as you interact and move through the world.
But the weirdest part is that it doesn’t affect all of us equally.
Many of us are not having issues despite still being filled and at max, with high memory temps. Mine has been perfectly fine, which makes it all the more annoying and puzzling, despite my testing showing the same results that those with issues have. Ugh.
I did take steps to protect my card from any long term damage as a result of this problem, but we shouldn’t have to be doing that. I say shouldn’t because this game has been one of the most hardware demanding games I have seen.
And its not like the overall game is actually taxing to run! But handling the assets is just hammering them.
I even took a chance last night and hooked up a 4K 46" Samsung TV (60hz) and ran it at a 4K res, 60FPS capped, just to see if I could finally run into the same issues a lot were that had the larger screen resolutions.
Nope. Ran for 2 hours, VRAM all maxed out no problems. I saw about a 3-5C increase in temps, but other than that? Notta. Had to make my mouse pointer bigger though, it was so tiny on that screen. LOL
I said this in another thread, I wish I had one of these that was buggered to experiment on. *sigh
No, we should not have to be doing this. Crazy conspiracy theory time. Maybe there is some undercover deal with microsoft going on, to tax peoples setups as hard as possible, bricking the entire 3000 series…since they was poorly and cheaply made. Why? To make more money of course. Because to some people, millions upon millions is just not enough.
Yeah well I did say it was crazy. But man history is repeating itself here. New world had these issues with bricking cards, D2R to a lesser extent as well, theres no reason why all these new games have to be so incredibly hard on peoples hardware…unless there was another reason for it of course.
Or maybe they are just trying to push the technological agenda we fully cannot understand yet. There is something going on thats all I know.
I was able to play the game for hours until yesterday. Not sure what changed, but I’ve had this memory leak issue with my vram (7900XT) constantly over the last two days. Memory fills up over 20-30 minutes, stuttering starts, game freezes and crashes. Not sure what could have changed…
Please stop calling it a leak. Its not. I have extensively tested this.
A leak (for memory) is when a running program actively increase memory without any additional input. If you fresh start a game, and just stand still, the memory does not go up, outside of the occasional player walking past you. It will not increase, not move, even if I stand still for 10+ minutes. I spent a few days testing to be sure. No leak.
But, once you move around, go out of town, etc, the memory slowly fills up, till it hits the limit, then you see your system memory start to increase.
It is moving assets into VRAM as you move through the game. This is normal, even though for this game its beating up the VRAM and heating it bad.
The crappy part, is that some systems don’t like this behavior to the point where they choke on it and start acting up, while many others seem to continue on oblivious to the VRAM bashing. It makes no logical sense.
But its not a leak. Sorry, I’m just tired of the mis-information.
I guess in the end it doesn’t really matter if its a leak or asset handling. It has an issue regardless.
Hopefully they will get it fixed or addressed somehow soon.
When troubleshooting this I’ve been looking at readings from afterburner but started using task manager as well and noticed something. My shared VRAM is between 0.4-0.6GB out of 8 at baseline after rebooting and idk why. It may be possible to buy more time between changing texture settings or even avoid stutters altogether if I could reduce that baseline shared RAM to 0. I get stutters when total VRAM passes 9GB.
I assume the reason that 9GB and up introduces stutters is that at that point my system is using too much shared RAM. It’s just an 8GB card and I’ve got 16GB RAM.
You see, I was starting to think about when dealing with cards that have more than 8, and you pass the 8 on the card, it starts to act up. But we both have 8, mine works fine, yours starts stuttering.
With the shared memory, I’m pushing about double that. At max after several hours of playing, my system memory use tops out at 17GB and about 7.5GB on the card. But that includes everything running on the system.
And people like me with 32 and even some with 64 have been having issues, so having 16 isn’t a problem really either, outside of it being the minimum I would recommend for this game.
Wish I could post screenshots here. I don’t think we’re talking about the same shared RAM. It’s under the performance tab of task manager > GPU, at the bottom.
Also I’ve no doubt my system should be fine to the run the game as is, I’m looking for a work around until Blizzard pushes a fix through. Medium textures are gross to look at.
Same issue here with an RTX 3080 Ti (12GB of VRAM) and 64 GB of RAM.
I had to swap textures to High to avoid the pretty frequent stuttering.
I’m pretty sure Blizzard can fix this by deleting not recently accessed textures as it looks everything is well managed in the scene during a few minutes of playtime, but it keeps building up as you move through environments. So it’s a matter of time to have in cache more than you card can handle (unless there is a card that can have the whole game textures in cache). Another scenario is VRAM-RAM transitioning that should be improved.
on Ultra and High i can play for about 30 - 90 Minutes and than suddenly i get locked at 5 - 15 FPS. Reloading Textures, so swapping from ultra down to high and than up to Ultra fixes it for approx. 30 Minutes but than it just occurs again.
Have to play on Medium to experience no stutters whatsoever.
Extremely High VRAM Usage
Starting to believe, the only way to get them notice this is that everyone creates a new thread entitled VRAM ISSUE READ THIS or something similar.
Inside the body of the post, have links to the 2 threads that have over 1000’s replies 10’s thousands of views
That way having 3-5 pages of VRAM ISSUE READ THIS , they can’t deny they’ve missed it.
Whilst I don’t usually condone spam, this may be a last resort and of course there are separate unrelated issues for other users which I don’t want to get overlooked either but FFS on our last tether with this…
(this post was made in jest ofc, as I find it comical how Blizzard have blatantly ignored user feedback since closed BETA)
I want some of you to try an experiment, but only if you feel comfortable with it:
First off, check your swap file settings on your system. They should be set to the same drive as the OS or the fastest drive you have.
Then, I want you to increase the swap file, set it to the recommended size, or higher, but don’t go too high. But higher than it defaults to. I mean mine recommends about 5GB, and is auto set to 2GB. (Actually that’s kinda low to me in my mind, but its Windows 11)
Set it for now (as a test) to 16GB. (16384MB)
If you need instructions on how, well they are all over the internet.
Now. If this does nothing, or seems to make it worse, then we are going to go the other way and shrink it.
In those cases, try 2048MB, (2GB) which is what I currently have and mine works. I also have 32GB of memory and a 3070Ti with 8GB of VRAM.
This is not a good thing to do on SSD or NVMe drive really. These things have a limited amount of wipes / writes / w/e. Its not going to kill my drive right away or anything like that…but no thx.
I will listen to your results however. I think I see where your going with this.
Yeah, its not something I’m recommending as a permanent fix, but I’m trying to see if it even affects the issue. If so, its something to help us understand the problem.
As for drive wear, I have replaced drives due to upgrades before I have actually had one wear out. In fact, I’m not sure I have yet to see one that was wore out. But I have had them simply fail. lol
A memory leak is when the system does not reclaim memory. It may or may not go up over time without input. If the system is not reclaiming memory it is by definition a memory leak.
I have 64gb ram, 1080ti and 5900x+ 3440x1440p - game installed on NVME SSD PCI4 - play hours with not issues, sometimes when going through new areas i get a few stutters but then its back to normal, vram usage is around 9 to 10.8gb (ultra textures, almost max settings + fsr quality - 90-130ps - avg 110)
My GPU is RTX 4090 and I can play the game for hours on max settings only if textures are set on High quality. I had encountered issues during the first day of playing before Blizzard had delivered all the patches around launch and had to reduce the textures from Ultra to High to make it playable, in which case the game consumes around 12-14 GB VRAM. I decided today to try the game with Ultra textures again. In 15 minutes the VRAM usage had reached 20 GB and I am sure that in another 15 minutes the game would have claimed all 24 GB on my GPU.
The gameplay is good but the level of optimization for high-end hardware is really ridiculous. I could hardly believe that there will be a game who could eat all the memory on a RTX 4090.
I tried changing the page file and here’s what happened.
When the page file is set to auto, what I have it set to by default, it’s at around 23.5 GB which is 1.5 times my total physical RAM. Seems excessive to me but OK.
When the size is set to 2024 MB, D4 won’t even launch. I get error messages that “D4 has run out of memory”.
When I increase the size to 2911 MB which is what my system lists as being “recommended” in the page file UI, the game will launch but then I can’t pass the login screen. The game will crash and I get a pop up labeled “Fenris”.
I tried using 4048 MB as well but got the Fenris error once more.
8096 got me to character select but then screen froze.
Leaving the page file on auto lets me back in no problem.
and of course there are separate unrelated issues for other users which I don’t want to get overlooked either but FFS on our last tether with this…