Search Issue Tracker

By Design

Votes

0

Found in

2021.3.16f1

2022.2.2f1

2023.1.0a26

2023.2.0a1

Issue ID

UUM-25385

Regression

No

Memory usage increases by 100Mb in mobile builds until a crash occurs when memory calculations are repeated

-

How to reproduce:
1. Open the “MemoryOverflow.zip” project
2. Connect a mobile device to your machine
3. In Build Settings check Development Build, Autoconnect Profiler, Deep Profiling Support
4. In the Run Device dropdown menu select a device.
5. Click Build and Run
6. When the build loads on the device, tap on the screen and observe the Profiler in the Editor

Expected result: GC Used Memory should stay stable around 500Mb.
Actual result: GC Used Memory increases ~100Mb with a screen tap until the Player crashes.

Reproducible with: 2021.3.16f1, 2022.1.24f1, 2022.2.2f1, 2023.1.0a26
Could not test with: 2020.3.44f1 (Custom script errors)

Reproducible with these devices:
VLNQA00331 - Huawei P20 lite (ANE-LX1), Android 9, CPU: HiSilicon Kirin 659, GPU: Mali-T830
VLNQA00334 - Xiaomi Mi A3 (Mi A3), Android 11, CPU: Snapdragon 665 SM6125, GPU: Adreno (TM) 610
VLNQA00134 - Samsung Galaxy S8 (SM-G950F), Android 9, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
VLNQA00494 - iPhone 14 Pro Max, 16.0.3 iOS
VLNQA00358 - iPhone 12, 14.1 iOS
VLNQA00392 - iPad (9th generation), 15.0 iOS

  1. Resolution Note:

    The Issue is by design and is related to the managed heap fragmentation to interleaving pattern of large and small allocations of different lifecycle.

    If it is possible to reduce the allocations or change the lifecycle of the allocations, like making them permanent, may help.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.