# UE 5.8.2 Vulkan memory leak, consumed 114GB RAM and killed by OOM

**URL:** <https://forums.unrealengine.com/t/ue-5-8-2-vulkan-memory-leak-consumed-114gb-ram-and-killed-by-oom/2764868>\
**Category:** Issues and Bug Reporting (Unreal Engine)\
**Tags:** unreal-engine, open, crash, bug-report, CPP\
**Created:** [September 11, 2026, 7:30pm UTC](https://forums.unrealengine.com/t/ue-5-8-2-vulkan-memory-leak-consumed-114gb-ram-and-killed-by-oom/2764868 "2026-09-11T19:30:32Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![AvengerZero1](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/avengerzero1/32/1203909_2.png) [@AvengerZero1](https://forums.unrealengine.com/u/AvengerZero1)\
**Post date:** [September 11, 2026, 7:30pm UTC](https://forums.unrealengine.com/t/ue-5-8-2-vulkan-memory-leak-consumed-114gb-ram-and-killed-by-oom/2764868/1 "2026-09-11T19:30:32Z")

</div>

### Summary

Hi!

We found that on Linux Vulkan, UE 5.8.2 leaks RAM on every parallel render pass.

It was confirmed on 2 separate machines with different GPUs. Occurs in both 5.8.0 and 5.8.2.

`RHIBeginParallelRenderPass()` does new `FVulkanDynamicRenderingInfo()`. RHIEndParallelRenderPass() deletes CurrentParallelRenderPassInfo and leaves DynamicRenderingInfo behind. FVulkanParallelRenderPassInfo has no destructor. File: Engine/Source/Runtime/VulkanRHI/Private/VulkanContext.cpp.

We saw it on two Linux machines running a packaged offscreen project, with several SceneCaptures and hardware ray-traced LiDAR:

- `machine1`: process grew to ~114 GB and the kernel OOM-killed it.
- `machine2`: anonymous RSS grew ~1.5 GB/h. Insights + addr2line on matching debug symbols pointed at FVulkanCommandListContext::RHIBeginParallelRenderPass - operator new.

Workaround:  
we tested r.Vulkan.AllowDynamicRendering=0, which reduced memory leak from about 1.5GB/h to 0.27 GB/h

### What Type of Bug are you experiencing?

Simulation

### Steps to Reproduce

1. Package a Linux Vulkan build of a project that uses parallel render passes (SceneCapture / hardware ray tracing is enough).
2. Run it offscreen for 20+ minutes (-RenderOffscreen).
3. Watch process RSS / anonymous memory.

Optional: Insights memory trace, then addr2line on RHIBeginParallelRenderPass.

Optional: r.Vulkan.AllowDynamicRendering=0 at startup and repeat.

### Expected Result

No memory leak

### Observed Result

RSS climbs about 1.5 GiB/h (on 2 separate machines). Same binary on sw-perc-1 grew to ~114 GB and was OOM-killed. Trace shows RHIBeginParallelRenderPass → operator new. r.Vulkan.AllowDynamicRendering=0 drops growth to ~0.27 GiB/h. Still present in 5.8.0 and 5.8.2 source.

### Affects Versions

5.8

### Platform(s)

Linux

### Additional Notes

Proposed fix:

```auto
From: Filip Kubicz <filip@kubicz.engineer>
Date: Fri, 11 Sep 2026 12:37:00 +0200
Subject: [PATCH] VulkanRHI: free FVulkanDynamicRenderingInfo on parallel pass end
RHIBeginParallelRenderPass heap-allocates DynamicRenderingInfo.
RHIEndParallelRenderPass only deletes CurrentParallelRenderPassInfo,
so the inner object leaks every pass.
---
 Engine/Source/Runtime/VulkanRHI/Private/VulkanContext.h | 5 +++++
 1 file changed, 5 insertions(+)
diff --git a/Engine/Source/Runtime/VulkanRHI/Private/VulkanContext.h b/Engine/Source/Runtime/VulkanRHI/Private/VulkanContext.h
index 0000000..1111111 100644
--- a/Engine/Source/Runtime/VulkanRHI/Private/VulkanContext.h
+++ b/Engine/Source/Runtime/VulkanRHI/Private/VulkanContext.h
@@ -49,6 +49,11 @@
 struct FVulkanParallelRenderPassInfo
 {
 	VkRenderPass RenderPassHandle = VK_NULL_HANDLE;
 	FVulkanDynamicRenderingInfo* DynamicRenderingInfo = nullptr;
 	TArray<FVulkanPayload*> SecondaryPayloads;
 	std::atomic<int32> NumParallelContexts = 0;
+
+	~FVulkanParallelRenderPassInfo()
+	{
+ delete DynamicRenderingInfo;
+	}
 };

```

---

<div class="post-metadata">

**Author:** ![AvengerZero1](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/avengerzero1/32/1203909_2.png) [@AvengerZero1](https://forums.unrealengine.com/u/AvengerZero1)\
**Post date:** [September 14, 2026, 6:43pm UTC](https://forums.unrealengine.com/t/ue-5-8-2-vulkan-memory-leak-consumed-114gb-ram-and-killed-by-oom/2764868/2 "2026-09-14T18:43:05Z")

</div>

Fix proposed above confirmed to fix the memory leak. Please package it into Unreal Engine release.

---

<div class="post-metadata">

**Author:** ![YairTrim](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@YairTrim](https://forums.unrealengine.com/u/YairTrim)\
**Post date:** [September 16, 2026, 7:40pm UTC](https://forums.unrealengine.com/t/ue-5-8-2-vulkan-memory-leak-consumed-114gb-ram-and-killed-by-oom/2764868/5 "2026-09-16T19:40:58Z")

</div>

Independent reproduction, different workload: no SceneCapture, no ray tracing, empty level

Confirming this on 5.8.2 CL 56702186, Linux (Ubuntu 22.04, kernel 6.8), Vulkan, NVIDIA 580.x, in a packaged Development build running windowed at 1280x720 on a near-empty template map. No SceneCaptures, no hardware ray tracing, no LiDAR. Worth noting because the repro steps above make those look relevant - they aren’t. This fires on any parallel raster pass.

Measured with RssAnon from /proc//status rather than VmRSS, so page cache and mapped pages are excluded. Sampled every 10 s over 12 minutes, steady state after a 60 s warm-up:

- Default: RssAnon +44.5 MB/min, LLM tag SceneRender +36.4 MB/min
- With r.Vulkan.AllowDynamicRendering=0: RssAnon +1.6 MB/min, LLM tag SceneRender +0.0 MB/min

RssFile and thread count are flat throughout, so it is purely anonymous heap. A /proc//smaps diff shows the growth arriving as a stream of 8256 kB MallocBinned2 pool chunks (FMallocBinned2::MallocExternalSmall → FPooledVirtualMemoryAllocator::CreatePool), i.e. a steady drip of small allocations rather than anything large.

The leak is per frame, not per unit time. Capping with t.MaxFPS 10 dropped SceneRender growth to +3.9 MB/min, which works out to roughly 6.5 KB retained per rendered frame. Measured frame rate at default was 102.6 fps, and 36.4 MB/min at that rate gives 5.9 KB/frame - the two agree within 10%. That is consistent with ~1 KB per leaked FVulkanDynamicRenderingInfo times the number of parallel render passes per frame (about 6 on this map).

Two things that may help triage:

Disabling dynamic rendering eliminated it completely here - SceneRender went from +36.4 to +0.0 MB/min - rather than the ~82% reduction reported above. The residual +1.6 MB/min in my case is LLM tag RHIMisc and is present identically with the workaround on or off, so it looks like a separate and much smaller issue.

The growth is attributed by the low level memory tracker to ELLMTag::SceneRender, not RHIMisc. That surprised me, since RHIBeginParallelRenderPass is reached through an EnqueueLambda at command list execution rather than inside the render thread’s SceneRender scope, but the A/B is unambiguous: turning the CVar off takes that tag to exactly zero.

Also ruled out by A/B on the same build, each identical to control: r.PSOPrecaching=0 gave +36.4 MB/min, r.Shadow.Virtual.Enable=0 gave +36.6 MB/min, and Lumen’s own LLM tag never moved off 2.1 MB for the whole run.

Confirming the mechanism is present in the stock 5.8.2 binary release as shipped: FVulkanParallelRenderPassInfo in VulkanContext.h declares no destructor, RHIBeginParallelRenderPass allocates DynamicRenderingInfo at VulkanContext.cpp:585 under HasKHRDynamicRendering, and RHIEndParallelRenderPass ends at VulkanContext.cpp:667 with delete CurrentParallelRenderPassInfo only.

One note for anyone else applying the workaround: r.Vulkan.AllowDynamicRendering is ECVF\_ReadOnly, so it has to come from an ini or -dpcvars on the command line. Setting it via -ExecCmds or the in-game console is too late to have any effect. A quick way to confirm it took: with the CVar at 0 the base VK\_KHR\_dynamic\_rendering extension is still loaded (Maintenance5 depends on it) but VK\_KHR\_dynamic\_rendering\_local\_read and VK\_EXT\_dynamic\_rendering\_unused\_attachments drop out of the enabled extension list in the log.

---

<div class="post-metadata">

**Author:** ![Flak](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/flak/32/769441_2.png) [@Flak](https://forums.unrealengine.com/u/Flak)\
**Post date:** [September 17, 2026, 12:33pm UTC](https://forums.unrealengine.com/t/ue-5-8-2-vulkan-memory-leak-consumed-114gb-ram-and-killed-by-oom/2764868/6 "2026-09-17T12:33:17Z")

</div>

Thank you, I’ll get this to the correct team for review.

---

<div class="post-metadata">

**Author:** ![Bug-Reporter](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/bug-reporter/32/1223650_2.png) [@Bug-Reporter](https://forums.unrealengine.com/u/Bug-Reporter)\
**Post date:** [September 22, 2026, 2:01pm UTC](https://forums.unrealengine.com/t/ue-5-8-2-vulkan-memory-leak-consumed-114gb-ram-and-killed-by-oom/2764868/8 "2026-09-22T14:01:23Z")

</div>

UE-396792 has been ‘Closed’ as a duplicate of an existing known issue. Origin Issue: UE-392081

---

<div class="post-metadata">

**Author:** ![Bug-Reporter](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/bug-reporter/32/1223650_2.png) [@Bug-Reporter](https://forums.unrealengine.com/u/Bug-Reporter)\
**Post date:** [September 22, 2026, 2:01pm UTC](https://forums.unrealengine.com/t/ue-5-8-2-vulkan-memory-leak-consumed-114gb-ram-and-killed-by-oom/2764868/9 "2026-09-22T14:01:23Z")

</div>

UE-392081’s status has changed to ‘Ready for QA’. A member of the QA department is investigating the issue.

---

<div class="post-metadata">

**Author:** ![LevelWizard2249](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@LevelWizard2249](https://forums.unrealengine.com/u/LevelWizard2249)\
**Post date:** [September 30, 2026, 3:42pm UTC](https://forums.unrealengine.com/t/ue-5-8-2-vulkan-memory-leak-consumed-114gb-ram-and-killed-by-oom/2764868/10 "2026-09-30T15:42:05Z")

</div>

I can independently confirm this issue on UE 5.8 with a different project/workload.

I originally investigated a long-running packaged Unreal application where performance gradually degraded over time. Using Unreal Memory Insights, I traced continuous `SceneRender` memory growth to repeated allocations through the Vulkan parallel render-pass path, including:

`FVulkanCommandListContext::RHIBeginParallelRenderPass`  
→ `FVulkanDynamicRenderingInfo`  
→ repeated ~900-byte allocations

Reviewing the UE 5.8 VulkanRHI source also led me to the same ownership/lifetime path described in this report, where `DynamicRenderingInfo` is allocated separately inside `FVulkanParallelRenderPassInfo`.

I then performed an A/B test using the same packaged application:

`r.Vulkan.RHIThread=2`  
→ SceneRender growth approximately **21 MB/min**

`r.Vulkan.RHIThread=1`  
→ SceneRender growth approximately **0 MB/min**

As a longer confirmation with `r.Vulkan.RHIThread=1`, SceneRender remained effectively flat during a 5-minute run:

**12.85 MB → 12.83 MB**

This was repeatable and strongly suggests that the retained allocations are associated with the Vulkan parallel/RHI execution path rather than application-level state accumulation.

This appears consistent with the `FVulkanDynamicRenderingInfo` lifetime issue already identified in this thread and may provide an additional reproduction/configuration for **UE-392081**.

I can provide Memory Insights captures, allocation-stack screenshots, hardware/OS details, and additional longer-duration A/B results if useful for QA.
