WoW Forever FPS Drops Fix — The Beta Memory Leak Explained

WoW Forever frame rate that starts fine and collapses after 15–30 minutes is a client memory leak, not your hardware — and logging out to character select and back in restores it immediately. Community testing measured committed memory growing ~29 MB/min and dedicated VRAM ~12–15 MB/min, with frame rate falling from around 110 FPS to 40 FPS over 88 minutes. This guide covers the measured evidence, the working mitigations, and how to tell this apart from an actual hardware problem.

Performance recovers the moment you relog — which is the proof it isn’t your PC.

The 30-second fix

Log out to character select, then log back in. You don’t need to close the game.

In a measured case this single action:

• Dropped VRAM use from 6.24 GB to 4.58 GB
• Restored GPU utilization from 22% to 52%
• Returned frame rate to near its session-start value

If that restores your FPS, you’ve confirmed the diagnosis and you can stop troubleshooting hardware. Repeat it whenever performance sags — roughly every 30–60 minutes for most players.

The measured evidence

Community bug reporting against builds 1.60.1.69893 and 1.60.1.69913 (following the 18 September 2026 patch) documented steady, non-levelling growth:

Metric	Measured growth
Committed system memory	+29 MB/min while playing
Dedicated VRAM	+12 to +15 MB/min while playing
Handle count	+12/min — even while AFK
Frame rate	~110 → ~40 FPS over 88 minutes

The AFK handle growth is the telling detail: memory climbs even when you aren’t doing anything, which points at the client rather than at scene complexity or what you’re rendering.

There’s a second symptom worth recognising. As VRAM fills, the engine’s texture defragmenter kicks in and drops render scale from 98% to 75% once video memory hits its budget (reported at used:6.6GB budget:6.6GB). So the game also gets visibly blurrier as the session goes on — that’s the engine trying to cope, not a settings change you made.

Why changing graphics settings doesn’t help

This is the part that confuses people most, and it’s genuinely diagnostic: Low and Ultra produce near-identical frame rates.

Player reports from the beta:

• An RTX 5090 with a Ryzen 9 9950X3D at 25–30 FPS
• “40–50 fps with low settings and 40–50 with ultra settings”
• Multiple users stuck at 20–40 FPS regardless of quality preset

When quality settings make no difference and top-tier hardware performs the same as mid-range, you are not GPU-limited. Turning everything down is wasted effort here. The general principle — and how to confirm it on any game — is covered in why FPS drops after hours of gameplay, which uses this exact WoW data as one of its documented cases.

Other fixes players report working

Beyond the relog, these have produced large, specific gains in the beta:

1. Update your GPU drivers. One player went from 24 FPS to 100+ FPS after a driver update. This is the highest-value first step if you haven’t done it.
2. Delete the WoW cache folder and relaunch. Another reported going from 30–40 FPS to 144 FPS after clearing cache and restarting the launcher. Delete the Cache folder in your WoW install directory — the game rebuilds it.
3. Disable the Target Framerate setting. One player reported this “over doubled my FPS.” It’s an easy thing to test and costs nothing.
4. Close background applications. Overlays, browsers and capture software compete for the memory the leak is already eating into.
5. Cap your frame rate below your refresh rate for steadier pacing once you’re back at a decent baseline.

A note on honesty: some guides claim a Radeon-specific problem with Secondary Lighting. The primary Blizzard forum reports do not show a significant GPU brand difference — both NVIDIA (RTX 3090, RTX 5090) and AMD (RX 9060 XT) cards are affected. Treat brand-specific claims about this beta with caution.

Is it the leak, or something else?

Symptom	Cause	Fix
Fine at first, degrades over 15–30 min, recovers on relog	Memory leak	Relog; this guide
Bad immediately and constantly, never recovers	Drivers, cache, or Target Framerate	Fixes 1–3 above
Stutter only while moving, smooth standing still	Asset streaming / CPU-side hitching	Cache clear, SSD, frame cap
Random micro-stutter in every game	DPC latency / drivers	Fix high DPC latency
Hard crash with a VRAM error	VRAM exhausted	Out of video memory fix

The relog test is the cleanest separator. Failing or thermally throttling hardware does not recover because you returned to character select.

Where this stands

Blizzard has not formally confirmed a memory leak, although a fix has been reported as being on the roadmap. The issue remains unresolved in current beta builds.

Some perspective is fair here: WoW Forever is in beta, announced at BlizzCon on 12 September 2026, with the beta opening 17 September and full release scheduled for 4 November 2026. Progressive memory leaks are a common beta-build problem and usually get fixed before launch. The mitigations above are real and work now — but if you’re chasing the last of it on a beta client, some of it isn’t in your hands.

The short version

• Relog to character select to reclaim leaked memory — VRAM 6.24 → 4.58 GB in testing.
• Measured leak: ~29 MB/min RAM, ~12–15 MB/min VRAM, 110 → 40 FPS over 88 minutes.
• Low and Ultra give the same FPS — you aren’t GPU-limited, so don’t bother lowering settings.
• Update drivers (24 → 100+ FPS reported), delete the Cache folder, disable Target Framerate.
• Render getting blurry? That’s the texture defragmenter dropping render scale to 75%.
• Not confirmed fixed; launch is 4 November 2026.

Related: Best WoW Forever settings for FPS · Why FPS drops after hours of gameplay · Best tools to fix stuttering in games