Search Issue Tracker
Fixed in 5.0.0-pre.8
Fixed in 4.2.3
Votes
3
Found in [Package]
4.2.0-pre.7
Issue ID
1379235
Regression
Yes
[ARCore] [Android] Memory leak in XR application when using AROcclusionManager component
How to reproduce:
1. Open the attached project "1379235"
2. Change platform to Android
3. Open Build Settings and enable Development Build
4. Build and Run on Android device
5. Open Memory Profiler and connect to the Android device
6. In the Android app, go to Depth > Simple Occlusion and make sure the camera is not covered (the screen should not be black)
7. In the Memory Profiler window, press 'Capture' to take Snapshot
8. After 2 minutes, press 'Capture' again and compare both snapshots
Expected result: The memory went from ~460 MB to 520 MB
Actual result: The memory went from ~460 MB to 700 MB
Reproducible with: 4.2.0-pre.7 (2020.3.23f1), 4.2.1 (2020.3.23f1, 2021.2.5f1, 2022.1.0b1)
Not reproducible with: 4.1.3 (2019.4.33f1), 4.2.0-pre.5 (2020.3.23f1)
Notes:
- If the issue does not reproduce, the memory always stays at ~520 MB when testing for a longer time
- If the issue reproduces, the memory can go over 1 GB when testing ~4 minutes
- Does not reproduce on iOS
- If the camera is covered (black screen), it's harder to reproduce because the memory rises at significantly lower speeds (can be under 100 MB jump in 10 minutes)
-
s84s86xu3
Aug 02, 2022 09:55
This problem still occurs in my project... When there is an ARSession component in the scene, the memory will keep rising until the game crashes!!
Mobile device : samsung galaxy a32 5g
Unity version : Unity 2021.3.6f1
ARCore版本 : 4.2.3
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 5.0.0-pre.8):
Fixed in: 5.0.0-pre.8
Resolution Note (fix version 4.2.3):
Fixed in: 4.2.3