Is there an option/way to cap the amount of RAM WoW uses

So with the new memory leak going on, I’m having some trouble as I only have 16G of RAM. Normally I run at 3.0-3.7GB used with just battlenet up and no other applications. After the patch when I run wow it eventually climbs to 13+ GB (and will cap RAM if I run it too long) and when I exit out of WoW it jumps up to 15+ pushing a lot of work onto my swap space.

I was wondering if there is a command line option or way in Windows to set a maximum limit of RAM usage for WoW so it doesn’t kill my system either because I forget to watch the usage and it claims all the RAM I have or it gets too high and does that spike when I close it?

In this thread, I’m not looking for a means to fix the memory leak (other threads cover that), but more looking for a way to bandaid it until later on.

Did you try resetting your UI? I haven’t been able to replicate any memory leak issues.

Yes, I did. I even pulled out my existing install do a different drive and reinstalled a fresh copy with the same result.

I’m definitely not alone (I’ll put some links at the end if you need refs).

However, I’m not trying to troubleshoot it here. I’m more looking to see if I can bandaid it for now by capping the RAM allowed for WoW.

Do you know of a command line option or some method for me to cap memory usage?

Other folks seeing it:

https://www.reddit.com/r/wow/comments/17qjwb1/102_memory_leak/

Unfortunately it is a known issue and they are working on a fix. There was somewhat of a band-aid done this morning, but still no complete fix. Are you running DX12 or DX11? Do you have an AMD card? If you are running 11 and can run 12, try switching and lowering the graphics if needed. You can also try 11 Legacy and see if that helps. If you do have an AMD, however, I don’t recommend 12 as it’s currently having some known issues with 12.

Where is the issue acknowledged as known? Can you link?

I can’t reproduce it at all, even after 10+ hours in new zone.

I’m in a disc server with a senior dev and it just hasn’t been publicly acknowledged yet. They changed some stuff this morning for reset but nothing complete. Here is a bluepost about the similar issues (it seems to be a problem with DX11, 12, and interactions with AMD and other gpus.

Yeah I know you keep posting this. Until it’s a public post, it’s not confirmed. That link just says they’re looking into it, not accepting blame for the issue.

2 Likes

I have no reason to make anything up but go off. lmao

Just an update: While I didn’t find a way to limit RAM usage directly, blizzard acknowledged the leak in another thread and provided a command we can use to temporarily reset the memory consumption. See linked post below:

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.