Search Issue Tracker
By Design
Votes
0
Found in [Package]
0.6.0-preview.1
Issue ID
1402028
Regression
No
[Android] Untracked Memory increases for the first minute and when the app is sent to background and brought back up
How to reproduce:
1. Create a new Unity project
2. Open the Package Manager (Window->Package Manager)
3. Install Memory Profiler (In Package Manager top-left "+"->Add package by name...->"com.unity.memoryprofiler"->Add)
4. Open the Memory Profiler (Window->Analysis->Memory Profiler)
5. Open the Build Settings (File->Build Settings...)
6. Change the Platform to Android
7. Add an empty Scene to Scenes In Build
8. Check "Development Build" and "Autoconnect Profiler"
9. Build And Run
10. In the Memory Profiler press "Capture", wait a minute and press "Capture" again
11. On the device send the app to the background and bring it back again
12. Press "Capture" In the Memory Profiler
13. Repeat steps 11 and 12, 3-4 more times
14. Observe the Memory snapshot's "Untracked Memory"
Expected results: "Untracked Memory" doesn't increase in the Memory Snapshots
Actual results: "Untracked Memory" increases for the first minute (15-30MB) and increases after each time the app is sent to the background and brought back up
Reproducible with: 0.4.0-preview.1, 0.6.0-preview.1 (2019.4.37f1, 2020.3.32f1, 2021.2.17f1, 2022.1.0b12, 2022.2.0a8)
Could not test with: 0.2.10-preview.1 and earlier opening snapshot infinite loop
Reproducible with:
VLNQA00335, Samsung Galaxy S20+ 5G (SM-G986B), Android 10, CPU: Exynos 990, GPU: Mali-G77
----------, Oppo Reno Z 中国版 (PCDM10), Android 11, CPU: NOT FOUND, GPU: PowerVR Rogue GM9446
Not reproducible with:
Standalone
Could not test with:
iOS devices (Untracked Memory is shown as "Unkown")
Note:
- "Memory" Module in the Profiler does not show any memory increase
- The Untracked Memory does stop increasing after bringing back up the app ~5 time
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
Add comment