# Physics field clipmap buffer leaks when changing worlds 

**URL:** <https://forums.unrealengine.com/t/physics-field-clipmap-buffer-leaks-when-changing-worlds/2840671>\
**Category:** Platform & Builds\
**Tags:** unreal-engine, Epic-Pro-Support, question\
**Created:** [September 14, 2026, 1:29pm UTC](https://forums.unrealengine.com/t/physics-field-clipmap-buffer-leaks-when-changing-worlds/2840671 "2026-09-14T13:29:46Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [September 14, 2026, 1:29pm UTC](https://forums.unrealengine.com/t/physics-field-clipmap-buffer-leaks-when-changing-worlds/2840671/1 "2026-09-14T13:29:46Z")

</div>

Hi,

When smoke testing our project, we ran into memory leak issues. Upon investigation, I discovered at least one of them can be attributed to the physics field clipmap buffer not being cleaned up properly.

From what I can tell, the buffer is created at the start of the level together with the physics field component. Then, it’s referenced by both the associated UAV and SRV resources. However, for some reason, the SRV resource ref counter increases once too many, preventing proper deletion. As I’m not too familiar with the rendering pipeline, I don’t really know exactly how this happens, but I did notice that `FRHIResource::GatherResourcesToDelete` fails to delete the SRV the first frame.

I’ve discovered it in our local version of the engine, but I managed to reproduce it in vanilla 5.7.4. The test project is attached.

Is this a known issue, and if so, is there a fix for this available?

For the time being I’m planning on disabling physics field components altogether with `r.PhysicsField.EnableField`. From what I can tell at first glance, there isn’t anything that is actively using the physics field in our project.

[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [September 14, 2026, 1:29pm UTC](https://forums.unrealengine.com/t/physics-field-clipmap-buffer-leaks-when-changing-worlds/2840671/2 "2026-09-14T13:29:48Z")

</div>

**Steps to Reproduce**

1. Open a project (in -game mode)
2. Log transient resources using `rhi.DumpResourceMemory -csv all transient=yes`
3. Observe only one entry exists for `PhysicsField_ClipmapBuffer`.
4. Open another level.
5. Log transient resources again.
6. Observe there are now two entries.
7. Repeat until satisfied (or out of memory).  
[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [September 14, 2026, 1:31pm UTC](https://forums.unrealengine.com/t/physics-field-clipmap-buffer-leaks-when-changing-worlds/2840671/3 "2026-09-14T13:31:58Z")

</div>

I don’t see the attached project, so here it is

[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![Patrick\_Laflamme](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/patrick_laflamme/32/1036111_2.png) [@Patrick\_Laflamme](https://forums.unrealengine.com/u/Patrick_Laflamme)\
**Post date:** [September 15, 2026, 1:25pm UTC](https://forums.unrealengine.com/t/physics-field-clipmap-buffer-leaks-when-changing-worlds/2840671/4 "2026-09-15T13:25:50Z")

</div>

Hi,

I recently tracked this ~10 MB leak and I found the fix on //UE5/Main, CL 51168522 . In my test case, the physics field leak came from:

```auto
UWorld::FXSystem is a RAW pointer World.h:1857
    → the world's FFXSystemSet / FFXSystem /
      FNiagaraGpuComputeDispatch are NEVER DESTROYED UE-315065
    → ~FNiagaraGpuComputeDispatch never runs,
      so AsyncGpuTraceHelper->Reset() never runs NiagaraGpuComputeDispatch.cpp:252
    → FNiagaraAsyncGpuTraceProviderGsdf::m_ViewUniformBuffer
      keeps the dying world's LAST-FRAME view UB forever NiagaraAsyncGpuTraceProviderGsdf.cpp:120
    → FRHIUniformBuffer::ResourceTable holds the clipmap SRV
    → SRV holds the FRHIBuffer, 10,485,760 B

```

Once I integrated CL 51168522, the leak was gone in my UE 5.7 test project. Can you integrate this CL and let me know if this works for you?

Regards,

Patrick

[Attachment Removed]
