Just got a memory usage warning while running 32 gigs of ram. Game has been crashing (stops responding) in about 1 per day after the 11.0 patch.
Game gave this message:
Not enough memory. Please refer to https://battle.net/support/article/6926 to find out how to reduce your memory usage.
It was the same for me this morning, my pc is fine. I did a restart of wow and itās all been good since. The memory on my pc is fine so I think you can disregard their suggestion of buying a new pc lol.
Had the same warning last night, and there are several reports of it happening both on the NA forums and on reddit, so itās definitely an issue with this weekās update. I run a minimal amount of addons (DBM and RCLC, thats it) which are all updated for the patch, so I doubt itās an addon issue.
Thereās posts of it happening in Valdrakken, during Radiant Echoes, on the character select screen. Personally I had it happen doing my mount farming in Freehold, which is all Iām logging on for currently. So it doesnāt seem to matter what youāre doing or where.
Thereās people saying itās a result of a render scale above 100%, but Iāve never upped mine above that so itās not that either.
Everything just leads me to believe the patch messed something up outside of our control.
Same issue here, had the game crash 3 times yesterday due to this issue, tried running more intensive games and they run fine no crashes.
ItĀ“s definitely a patch issue. ThereĀ“s no realistic way WoW should be causing memory size related issues on a machine with 128 GB ā¦ itĀ“s probably an overflow or leak issue, itĀ“s easy for those to weasel their way in to a row of patches that updates the engine among other things. 
And there are other problems, like mini-lags everytime you transfer from subzone to subzone, or yesterday night literally half of my raid team was suddenly disconnected AND left the group within 1 sec during a bossfight, and it wasnĀ“t some sort of synchronized ragequit, they were all back 1 minute later after we reinvited them.
And that, folks, is why itĀ“s a really, REALLY bad idea to not have this pre-Expansion month, because legitimately game breaking issues like this on launch day would be an absolute catastrophe, as people already whine enough about features they didnĀ“t even have for 20 years like currency transfer not working properly for 2-3 days like itĀ“s the only reason they ever played the game. 
Yeah same thingās happening to me. Got the error a few times and now I keep dc-ing with no error given or stuck in not responding. Just been questing in Ohnāahran Plains.
Same here - happens since the new patch came out. With or with deactivated addons - makes no difference at all. It just happens after some time - can be 1 hour, can be 3 hours. 5 times so far in 30 Hours.
Same here. I can run 10 instances of the game simultaneously RAM and VRAM wise and am on a vanilla install yet the game crashes with out of memory error.
Someone messed up the game code.
Same issue here. I never had any memory issues since years, and suddently, since last patch, the game crashed 4 times, everytime when I was in a raid, in Zaralek Cavern, for the boss fight.
Tried to cleanup windows as much as I can, removed all addons, but sometimes the memory leaks just happen, and the game crash.
Same happened to me today for a first time. Was AFK playing Pandaria Remix, game was even out of focus capped to 30 fps when out of memory error happened. Was worried that its one of the Intel instability symptoms because ppl often mention out of memory errors. I was using DX12 so its not DX11 legacy memory issue.
Edit. Monitoring Virtual Memory Committed in HWiNFO shows usually 16 GB allocated but when playing WoW it can spike even to 90 GB.
Out of memory: Killed process 7702 (WoW.exe) total-vm:58858776kB
Randomly, WoW attempts to allocate memory sizes that it should not require. Within 10 seconds I went from an average of 9 gigs of virtual memory dedicated to WoW, to over 58 gigs being allocated! Something is very wrong.
Same here, having this issue about 3 days
Iām having the same problem with memory leaks for two days as well, with both retail and Cataclysm classic
I came here for some other reasons, but seeing this post disembarrassed me. I have the same issue since 2-3 days, and was thinking about to buy some more RAM ( got 16 Gb right now). It could be expanded anyway, but still, itās good to know that the problem is not on my side.
Definitely a memory leak issue with WoW since the patch on 14/08. I have 32gb with 20gb assigned as virtual memory and while the game hasnāt got to the point of crashing, it is spamming my event viewer with thousands and thousands of Resource-Exhaustion-Detector events, citing WoW as a big consumer of memory. Not an addon problem, not a Dx11/Dx12 selection problem (Iām on Dx12 and people keep saying to swap to that to fix lmao), but a problem with the game itself. The only slight work around Iāve heard of is the /console gxrestart but Iām not sure how effective that really is. It seems to be more of a short period massive spike, than a constantly growing memory usage issue.
Same here as well. 32 gigs
reporting in, just had a nice memory leak happening and wow spiked to 26gb while doing vendor trading.
tech details: 32gb, running through wine. so not windows specific if anyone is wondering. Itās a game issue, it always is no matter how often they tell us to " just click repair and reinstall ".
would be nice if there was some quality control or acknowledgement from blizzard, both are be preferred, one is fine though.
Same here . happened to me and my friend today for like +10 times
games stops and u get the memory error then u have to stop the game process !
ā¦
Same here, seems fine first - then bam, 32GB is gone and wow is eating my swap.
Also happens in classic (SoD)
I found the culprit: https://www.wowhead.com/npc=224593/memory-leak
Same problem here. My game client crashed multiple times during M+ runs and raids. One time I was just standing afk in Valdrakken. Sometimes it crashes after like 30min, sometimes after 2h. I logged my RAM usage and noticed that my free memory dropped from 15GB to 0 in a matter of 2 seconds before the crash happened. Using DX12.