One of Blizzard's largest dedicated PC bug threads for the issue now sits at 508 replies and almost 20,000 views. The thread itself dates back to May 2025, when players documented system memory jumping to 15–20 GB within minutes, VRAM increasing with town portals and zone transitions, and crashes arriving after 15–30 minutes. Blizzard acknowledged the reports at the time and asked players to submit crash IDs. More than a year later, the same thread remains one of the most viewed topics in Diablo IV's PC Bug Report section, while fresh August 2026 posts continue describing high RAM and VRAM usage, severe stuttering and performance degradation.
That does not mean every current Diablo IV crash comes from one giant unresolved memory leak. PC performance problems can involve drivers, DirectStorage, texture settings, hardware configurations, overlays and plenty of other variables. But it does mean players have been describing the same basic pattern for an awfully long time.
The Original Report Was Extremely Specific
The major thread began with a player who had already submitted a support ticket and included a crash ID. Their measurements were not particularly subtle. System RAM reportedly climbed to 15–20 GB within minutes, even while sitting at character selection. VRAM increased after town portals and zone transitions until it reached approximately 13–14 GB. Logging out did not release the accumulated memory, and the client eventually crashed with a Fenris dialog after roughly 15–30 minutes.
Other players quickly joined in with wildly different hardware. Reports included RTX 3070, RTX 4090 and RTX 5080 systems, Radeon cards, 16 GB systems, 32 GB systems, 64 GB systems and even one player with 128 GB of DDR5 memory. Some experienced complete crashes. Others reported enormous stutters, long freezes or degrading performance without the game actually closing.
One particularly useful reproduction involved simply teleporting between locations. A player with 32 GB RAM reported starting around 10 GB of system usage and watching another 500 MB to 1 GB disappear after each zone change until the system eventually crashed. That matches the original report's suspicion that old zone assets were not being fully released when new ones were loaded.
Blizzard responded on May 6, 2025, confirming that the team was investigating and specifically asking players to provide the crash IDs generated by the Fenris reporter. A second Blizzard post explained where those IDs could be found inside the Diablo IV installation folder.
So this was not merely a community theory that Blizzard never noticed.
Blizzard knew about the reports.
508 Replies Later, the Thread Is Still One of the Biggest PC Bug Reports
As of late August 2026, Blizzard's PC Bug Report category lists the memory leak thread with 508 replies and roughly 19,700 views. Its most recent activity is dated July 8, 2026, meaning the thread itself is not receiving daily replies anymore, but it survived through multiple seasons and remained active more than a year after the original report.
That longevity matters more than the raw reply count. A short-lived patch problem can produce hundreds of comments in a weekend before disappearing with the next hotfix. This discussion instead spans changes to the game, driver revisions, major content updates and entirely different hardware generations.
Players repeatedly return to the same description: Diablo IV starts normally, memory usage rises while playing, transitions make things worse, stuttering becomes more pronounced and restarting the client temporarily restores performance.
Temporary improvement after restarting is one of the classic reasons players interpret this behaviour as a memory-management issue. It does not prove the precise technical cause, but from the player's perspective the pattern is difficult to ignore. The computer has not changed. The build has not changed. Sanctuary has simply consumed enough memory for one evening and needs to be put back in its box.
Fresh August Reports Show the Broader Performance Problem Has Not Disappeared
The old mega-thread is not the only reason the subject is relevant again. On August 23, a new Technical Support post described severe stuttering and frame-time spikes in towns and crowded areas alongside high RAM and VRAM usage. The player was using an RTX 3060 with 12 GB VRAM and 16 GB system memory and specifically asked whether upgrading to 32 GB would meaningfully help or merely delay the underlying problem.
The discussion remained active through August 25.
Another July report is even more direct. A player with 32 GB RAM measured Diablo IV beginning with total system memory usage around 22 GB before steadily climbing until essentially all 32 GB were occupied. Windows eventually reported that Diablo IV had run out of memory. The player described this behaviour as returning after large content patches and expansions.
Those newer reports are not controlled proof that precisely the same bug from the 2025 thread remains untouched. They could represent related but technically distinct problems. That distinction matters. “Diablo IV has a memory leak” is a much broader claim than “multiple players continue reporting escalating memory consumption and performance degradation.”
The second statement is the one the public evidence supports.
Blizzard Has Been Making Performance and Stability Fixes
It would also be unfair to pretend Blizzard has spent the last year doing absolutely nothing about Diablo IV's PC performance. Patch notes throughout 2025 and 2026 repeatedly mention performance and stability improvements, and Blizzard has changed specific technology when it appeared connected to problems.
One particularly relevant example came in June 2025, when Blizzard disabled DirectStorage by default while investigating performance issues. Players with supported NVMe drives could manually re-enable it through a command-line argument, but Blizzard clearly considered the feature suspicious enough to remove from the default configuration during the investigation.
Later updates continued including general performance and stability improvements. The July 14, 2026 patch again listed “various performance and stability fixes.”
The problem is that broad stability notes make it difficult for players to know whether the particular RAM/VRAM behaviour they have been reporting is considered fixed, partially fixed or still under investigation.
That communication gap is part of why the memory leak discussion refuses to die.
Players Have Found Workarounds, but None Look Like a Universal Fix
Over the life of the thread, players have suggested almost every PC troubleshooting ritual imaginable: lowering texture quality, disabling Ray Tracing, rolling back NVIDIA drivers, clearing shader caches, increasing the Windows page file, disabling overlays, repairing game files, reinstalling Diablo IV and restarting the client periodically before memory usage becomes critical.
Some players report that lowering texture quality helps significantly. Others say disabling Ray Tracing reduces crashes. Some found better stability after changing NVIDIA drivers. Several report that increasing the page file allows Diablo IV to run for longer before failing.
The common problem is that these solutions are inconsistent.
A workaround that helps one RTX 3060 system may do nothing for another machine. A driver rollback can improve performance for one GPU generation while introducing completely different problems elsewhere. Increasing virtual memory can stop Windows from immediately running out of addressable memory, but if the game's memory consumption continues growing, the player may simply be buying more time before the same degradation occurs.
That is why “just add more RAM” is not a particularly satisfying answer. One contributor to the original thread reported the problem while using 128 GB of DDR5.
If Diablo IV can eventually make 128 GB feel nervous, the solution probably is not another trip to the RAM aisle.
This Is Especially Awkward for Steam Deck and Handheld Players
Memory pressure becomes even more obvious on handheld hardware, where system RAM and graphics memory effectively compete inside a much tighter budget. Earlier this year, Steam Deck owners reported Diablo IV crashing approximately every 30 minutes, with some players explicitly connecting the behaviour to the wider memory issue.
We recently covered how Diablo IV players say Steam Deck performance has become worse rather than better, despite the game having had years to mature on the platform. Memory management is particularly unforgiving there because a desktop PC with 32 or 64 GB has enormous overhead a handheld simply does not possess.
A desktop user can sometimes tolerate a leak by restarting the game every few hours.
A handheld crashing halfway through an activity every 30 minutes is considerably harder to call a workaround.
Zone Transitions Keep Appearing in Player Reports
One detail that repeatedly appears across reports is movement between areas. Town portals, entering dungeons, leaving dungeons, visiting crowded towns and moving through different zones are frequently associated with increasing memory usage or sudden performance drops.
That does not necessarily mean zone transitions themselves contain the bug. They naturally force Diablo IV to stream large amounts of textures, geometry, player cosmetics, monsters and environmental data. If a memory-management problem exists elsewhere in the pipeline, teleporting repeatedly is simply one of the fastest ways to expose it.
It also explains why a player can stand in one area for a while without obvious problems, then begin stuttering badly after an evening of Nightmare Dungeons, Helltides, boss runs and trips back to town.
Diablo IV is a game built around constant transitions.
“Stop teleporting” would be an unusual endgame strategy.
Not Every Stutter Is a Memory Leak
This is the point where terminology becomes important. Players understandably use “memory leak” as shorthand whenever RAM or VRAM usage becomes enormous, but high memory usage by itself does not prove a true software memory leak.
Modern games aggressively cache assets because unused RAM is not inherently useful RAM. A game can occupy large amounts of system memory or VRAM without anything technically being wrong, provided it releases memory when required and performance remains stable.
The suspicious behaviour begins when usage continuously increases, old memory appears not to be released, performance degrades over time and closing the application immediately restores the system.
That is why the original thread's teleport reproduction was useful. It attempted to demonstrate a pattern rather than simply posting a screenshot showing “Diablo IV uses 18 GB.”
Likewise, not every Fenris crash is proof of a memory leak. GPU driver failures, unstable overclocks, shader problems and corrupted files can produce similar symptoms. Blizzard's PC client runs across an enormous range of hardware, which makes separating engine-level problems from individual configurations genuinely difficult.
But 500 replies across dozens of different configurations are also difficult to dismiss as one person's broken PC.
Current Patch Notes Do Not Declare the Major Memory Issue Resolved
Blizzard's current Diablo IV patch notes contain multiple references to general performance and stability work, but there is no prominent entry saying that the longstanding RAM and VRAM escalation reports from the major thread have been definitively resolved.
That does not mean Blizzard has made no progress. The experience clearly varies by system, season and patch, and some contributors have reported periods where their crashes improved significantly.
It does mean players have no simple official line they can point to saying:
“Yes, this specific problem has been fixed.”
That ambiguity matters because fresh users experiencing similar symptoms naturally find the enormous old thread through search, see hundreds of matching reports and conclude that the same issue has been running continuously for years.
Maybe technically it has.
Maybe several different problems have produced similar symptoms.
From the outside, those two possibilities look remarkably similar.
Performance Bugs Are Different From Ordinary Diablo Bugs
Diablo IV can survive a Set Charm behaving incorrectly or a War Plans point refusing to unlock. Those bugs are annoying, but the player can usually continue doing something else while waiting for a fix.
Performance degradation is different.
If the game eventually stutters into single-digit frame times, freezes for several seconds or crashes to desktop, every activity becomes affected. Boss fights, Hardcore characters, timed Pit runs and long sessions all become risky.
We have spent much of Season 14 covering small systems that appear to lose track of their own state, including Talisman bonuses reportedly switching off during combat and progression counters becoming stuck. Those are frustrating because the game stops calculating one part of the character correctly.
A performance issue is the same philosophy applied to the entire client.
The build might still work.
The computer would simply like Diablo IV to leave.
The 500-Reply Thread Is Really a Communication Problem Now
Perhaps the most useful thing Blizzard could do is not another generic line about “various performance and stability improvements.” It would be a specific update explaining the status of the memory-management investigation.
Is the original issue considered fixed?
Were several separate problems identified?
Are particular GPU configurations still affected?
Is high VRAM use considered expected behaviour while the stuttering has another cause?
Is Blizzard still collecting Fenris crash reports related to escalating RAM usage?
Players can deal with complicated answers. What creates frustration is not knowing whether the thing they are troubleshooting is something Blizzard believes it already solved twelve months ago.
The original forum response showed Blizzard was looking at the reports. The 508 replies that followed show players kept looking too.
Three Years In, Diablo IV Should Not Need a Restart Ritual
Diablo IV is now a mature live-service game. Some technical problems are inevitable when major seasons add new content, new assets and new systems. PC development is messy, and a problem affecting one particular combination of hardware and drivers can be extraordinarily difficult to reproduce internally.
But memory behaviour that repeatedly becomes a community talking point across multiple seasons deserves more than folklore.
Players should not have to memorize whether this is the season where they need medium textures, Ray Tracing disabled, an old GPU driver, a giant page file and a ceremonial client restart after every third Pit run.
Maybe Diablo IV no longer has the exact memory leak documented in May 2025.
Maybe today's reports represent something different.
But with fresh complaints about high RAM and VRAM usage still appearing in August 2026, Blizzard has not yet reached the most important technical milestone:
making players stop asking.
Sources
Diablo IV Forums: Major Memory Leak — RAM + VRAM Escalation
Diablo IV Forums: Severe Stuttering and High RAM/VRAM Usage — August 2026
Diablo IV Forums: Memory Leak on PC — July 2026 Report
Blizzard: Current Diablo IV Patch Notes
Blizzard: Diablo IV Patch 2.2 — DirectStorage Performance Investigation
```
