The patch today added a new memory leak to the game. After roughly an hour of playing the game had used up all my 16GB of my RAM and crashed.
The leak is worse now. I can only play for about 1/2 hour before I run out of RAM.
I watched the game in task manager and even if I just sat in one spot doing nothing, the game ate up 1-2GB every 10 minutes.
This patch is pretty unplayable right now for my friends and me because of this.
8 Likes
Same issue, thought it was a graphics card issue at first, but task manager aimed the blame squarely at the game client chewing up 32 GB of system ram in about an hour and a half of game play. Not that the video card isn’t groaning under some kind of added load, but it is only dropping a frame here and there. Nothing like the bloated hog the game client has become.
5 Likes
this really needs to be resolved… has been ging on all day. No response and completely ignored
7 Likes
My PC has been crashing all day due to WoW memory leak. RAM usage keeps climbing and climbing until everything poops itself.
Blizzard can we please take a look at this issue finally?
9 Likes
Meanwhile I’m still waiting on them to fix a 1.5GB/hour memory leak with the crafting ui that’s been there since 10.0 launch day.
5 Likes
Just thought I would add that I am NOT using any addons. Someone in chat suggested I disable them, but there is nothing to disable for me or most of my friends.
7 Likes
Same issue for me. Never had this problem before.
5 Likes
/reload ui doesn’t fix it. The only way is to close the game client down every 45-60 mins in order to play.
Raiding? pfft don’t even waste your time.
3 Likes
checks calendar
3 Likes
I am also seeing this memory leak. In some cases it causes me to have to restart my machine because it slows my machine so much it can’t shutdown the application and I can’t load task manager. Fills my RAM to the brim.
1 Like
It’s much worse today than it was yesterday. At first I was able to play up to an hour before the game crashed. Today the longest I have played is 20 minutes and it causes my PC to lock up, requiring a power down.
At least this has convinced me NOT to waste money on the next expansion. If they aren’t going to fix memory leaks from two patches ago, then I doubt they will bother with this one either.
Good thing LoTRO launched a new expansion this week too, so I got something to play.
1 Like
Just to be clear, it’s not same leak
That’s my tweet btw.
I was also one of first to find this leak though, although at time i thought it was macOs only but seeing some windows reports now.
3 Likes
Yeah, I’m aware.
It’s a note on how this xpac keeps piling up leaks.
Like… how there’s a crafting ui leak (that leaks upon each individual item created) that’s been there since DF launch unfixed and leaks multiple GBs per hour. If you put a wotlk chef’s hat toy on and click create all for something like pebbled rock salts or assorted spices you’ll hit something like 5GB per hour leak versus 1.5GB per hour with default speed.
We’re starting a memory leak bug queue line here…
Mine being Crafting UI Leaks Memory A Lot since launch day.
1 Like
Keeps getting worse every day. Can’t play more than 10 minutes today before all my memory has been eaten up by WOW. I noticed that there were almost no other players in the new zone last night or today. I wonder if other people have given up on the game because of this bug. Never seen interest in a patch die off so fast.
2 Likes
So strange, I ended up fixing it by going to direct X12 from Direct X11. This has brought my memory use back to around 5gb. Many have said that by changing to Direct X11 from 12 was their fix, no idea how this works, but hey …
We’ve identified and are working on a fix for unbounded memory growth that’s affecting Windows users using DX11 and all Mac users.
We should ideally have a hotfix build deployed early next week with the fix.
In the meantime, typing /console gxrestart in chat should cause the client to jump back down to normal memory usage (but will keep growing again after).
On Windows, using DX12 or DX11 Legacy backends should avoid the bug all together.
For those curious about the code side of things, the bug was an std::deque::clear() call that was incorrectly placed in a code block that is only compiled in for internal clients. That made it so the bug never happened for us in internal testing but had the unbounded growth in public clients.
22 Likes
Yes - thank you finally!
I’m married, so I may have to check with my wife first, but as an early announcement, I may love you (Disclaimer: All declarations of love are subject to approval by spouse of the house. No guarantees or promises should not be inferred until such time an approval has been obtained).
4 Likes
This is not the case on windows unfortunately. I can’t avoid the memory leak by using any DX version. Thank you for the gxrestart command though, I’ll give that a try in the meantime.
4 Likes