Out of memory error - Diablo 4 crash

On the cutscene after the first dungeon my pc temporarily froze, and diablo reported “Out of Memory” and crashed. PC specs are:
CPU: AMD Ryzen 9 5900X
GPU: AMD Radeon 6800XT
32 GB RAM (system currently reports 11.5 GB in use, with D4 open in the Queue. At the moment D4 is using 3.6GBs only.

I guess some sort of memory leak or something but I’ll keep an eye on task manager once I’m back in.

Edit: Was in a coop game.

2 Likes

As I updated in another post (D4 out of memory - #25 by AaGeOn-21557) I reduced my graphics quality to medium, including textures which seems to be the big one following advice provided here (https://www.reddit.com/r/Diablo/comments/11tvsxa/massive_memory_leak/ ) and it seems to be stable. If it crashes again due to the same problem I will post further updates.

Give it a shot the next time you get back in…

Solo game. Same issue. I also have 32gb ram and I ran out of memory. Played on medium. System says I have 9gb running otherwise.

I had the same issue, but I also thought 32 GB Ram and 8 GB GPU Ram would be enough. Boy I was wrong. I wish I went to settings and set graphics to low…

It’s not a you thing. This is clearly a memory leak issue

1 Like

I TOO HAVE ENCOOUNTERED A “D4 OUT OF MEMORY MESSAGE”

This crashed my game as well. I have 16gb of system memory, and a graphics card that has 8gb all new and working fine until I tried the open beta.
Will we getting this fixed soon?

This week I’ve dropped the settings to medium and continued to reduce graphics and it’s still happening even with 32 GB of RAM and a 1080 Ti.

I have still tweaking settings but with an hour between logging it it’s difficult to track what works and what doesn’t. I had about an hours worth of stable gameplay before the last memory leak crash after reducing more settings like shadows and enabling vertical sync with an FPS lock of 60 Background/Foreground.

I’ve also found Alt-Tabbing out of D4 to cause this memory leak error to expedite to a crash. If anyone else has any other observations it would be good to post them.

Game crashed 3 times so far in an hour (or so) with Out of Mem, and I specifically play it on Medium\Low setting (VSync off). I have 32 GB RAM and 8GB on the graphics, and I also run the task manager to monitor their usage, its nowhere near 50% on any of those when it crashes. I am forced to play it 4K as I want to use windowed mode to access other things like browsers on my other monitors but browsers crash after a while and the PC just hangs sometimes where I have to physically restart it…

i recon all here and all in European forums who have this problem have 32GB of RAM.

Just saying

You wanna say that there is such thing as too much RAM. More RAM = More Problems :smile:

no… it seems as this was programmed by a practician , who not only doesn’t know about Memory Handling, but also there seem constellations,where the RAM is not only used, but there is a memory leak if this constellation is present.

Furthermore : On closing Diablo other Programs are affected, too : Chrome sometimes closes with D45, Discord, too, and this is UNCACCEPTABLE.

This Beta also seems to have a mucxh prior patch then last weeks beta. The Performance per se is horrible. I had several problems with stuttering, lag etc ,where there were good latencys, 3-4 k ram used, 40 % CPU usage, and 30 % GPU usage.

I can not explain why this happens except really rteally bad programming in this patch-level.

I have the same issue. 16GB RAM. Lowest possible graphic settings.
80% resolution.

Game crashes after few minutes of play.
Then back to queuing for 30min

I have 32gb and 16gb of Vram. At max setting this game is using a staggering 14-16 of my vram and around 20.6 of my ram. Is insane.

Just happend to me. Was about to kill a world boss and had it crash.

CPU: R9-5950x
Mem: 32 GB @ 3600mhz
GPU: RX 7900XTX 24GB VRAM
Running game at full spec on 3440x1440 res. I get this on varying spaces of time from 20 min after starting to play to several-several hours of play time (on rare occasion it actually won’t happen). This, it would seem to me, would be a coding issue where the game is not telling the system to dump files in the mem after them have been there for a while (like most games normally do) and instead the build up causes a crash. Not to say it’s overloading the system, more like the files inconsistencies are cause faults in the memory. I only think this because everyone on here so far has more than enough memory and no one is seeing the memory spike at crash.
Doesn’t really change anything. It still falls back to Blizzard for screwing up the games operation/function.

I had two crashes this evening. Ram reached almost 27GB out of 32 in my system this is crazy. clearly a memory leak. it would hang around 15GB normally for a hour then it would increase quickly then crash. This is only since the latest patch release.
Rx 6800 xt Nitro 16gb
G.Skill 3600 32gb