# Follow-up: \[IOS\] \[UE5.6.1\] Physical memory regression on IOS after upgrading to Unreal 5.6.1 

**URL:** <https://forums.unrealengine.com/t/follow-up-ios-ue5-6-1-physical-memory-regression-on-ios-after-upgrading-to-unreal-5-6-1/2762888>\
**Category:** Platform & Builds\
**Tags:** unreal-engine, Epic-Pro-Support, question\
**Created:** [July 17, 2026, 9:11pm UTC](https://forums.unrealengine.com/t/follow-up-ios-ue5-6-1-physical-memory-regression-on-ios-after-upgrading-to-unreal-5-6-1/2762888 "2026-07-17T21:11:00Z")\
**Posts on this page:** 3\
**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:** [July 17, 2026, 9:11pm UTC](https://forums.unrealengine.com/t/follow-up-ios-ue5-6-1-physical-memory-regression-on-ios-after-upgrading-to-unreal-5-6-1/2762888/1 "2026-07-17T21:11:00Z")

</div>

Following up on my thread about IOS memory usage: [Content removed]

I do believe I’ve narrowed down the issue:

```auto
UsePakFile=True
bUseIoStore=False
bUseZenStore=False

```

The long and short of it: UE5.6.1 changed the default to use AsyncLoadingThread2 even when not using IoStore. Without GUseOldLoaderAsFallback, the new codepath appears to create a spate of LinkerLoads that do not get discarded. As a result, the memory allocated by these LinkerLoads remains resident and raises our baseline memory enough to push the game into IOS jetsam territory:

+87 MB custom-version buffers

+76 MB pak-read buffers

+140 MB package-summary/export-hash family

I had noticed those allocations in Instruments but ruled them out as irrelevant because LinkerLoad is a normal part of the engine. It just took me a while to realise that these are normal during \*load time\*, just not past that. Toggling GUseOldLoaderAsFallback back on fixes the dangling allocations.

We’ll probably want to use IoStore at some point, but for now this mostly explains the memory regression.

---

<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:** [July 17, 2026, 9:11pm UTC](https://forums.unrealengine.com/t/follow-up-ios-ue5-6-1-physical-memory-regression-on-ios-after-upgrading-to-unreal-5-6-1/2762888/2 "2026-07-17T21:11:04Z")

</div>

**Steps to Reproduce**

---

<div class="post-metadata">

**Author:** ![step\_jac\_eg](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@step\_jac\_eg](https://forums.unrealengine.com/u/step_jac_eg)\
**Post date:** [August 6, 2026, 1:04pm UTC](https://forums.unrealengine.com/t/follow-up-ios-ue5-6-1-physical-memory-regression-on-ios-after-upgrading-to-unreal-5-6-1/2762888/3 "2026-08-06T13:04:22Z")

</div>

Thank you for sharing your findings Camille, will pass this on to the team.

Best regards.
