Search Issue Tracker

Won't Fix

Votes

0

Found in

2022.3.42f1

6000.0.15f1

Issue ID

UUM-77868

Regression

No

[Android] "/memfd:jit-cache" and "/memfd:jit-zygote-cache" heavy runtime memory usage when building to Android

--

-

Steps to reproduce:
1. Create a new project
2. Switch to Android and build
3. Open Memory Profiler
4. Capture a snapshot of the device
5. Navigate to "All of Memory -> Executables & Mapped"
6. Observe "/memfd:jit-cache" and "/memfd:jit-zygote-cache" taking up 128mb and 56mb respectively

Expected results: "/memfd:jit-cache" and "/memfd:jit-zygote-cache" are lower in memory usage than what is reported
Actual results: heavy runtime memory usage coming from a memfd:jit-cache when building to Android

Reproducible with: 2022.3.42f1, 6000.0.15f1
Couldn't Test on 2021.3.42f1 due to Memory Profiler not displaying "All Of Memory" -> "Executables and Mapped"

Reproducible with these devices
VLNQA00609 - Oculus Quest 3 (Quest 3), CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno 740, OS: 12
VLNQA00415 - Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650, OS: 12
VLNQA00528 - HMD Global Nokia G20 (Nokia G20), CPU: Mediatek MT6765G Helio G35 (12 nm), GPU: PowerVR Rogue GE8320, OS: 13
VLNQA00423 - Google Pixel 3 (Pixel 3), CPU: Snapdragon 845, GPU: Adreno 630, OS: 9
VLNQA00422 - Galaxy S21 Ultra 5G (SM-G998B), CPU: Exynos 2100, GPU: Mali-G78, OS: 11
VLNQA00381 - Xiaomi Redmi Note 8 Pro (Redmi Note 8 Pro), CPU: MediaTek Helios G90T MT6785T, GPU: Mali-G76 MC4, OS: 9
VLNQA00282 - Samsung Galaxy S10e USA (SM-G970U), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 9

Notes:
-Issue is reproducible on a new project
-Memory Profiler data attached "MemoryProfilerData.snap"

  1. Resolution Note:

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Our ISS customers’ bug reports have a higher weight than normal, and this is accounted for in the decision. We hope to be able to work with you on finding a suitable workaround in the short term. Today, however, we will be closing this case.

    Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

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.