Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X
Votes
0
Found in
2018.4
2019.4.4f1
2020.2
Issue ID
1267773
Regression
No
Total System Memory Usage in the profiler is very different with different devices with the same build
Steps to reproduce:
1. Open user's attached project "UnityMemoryTestURP.zip"
2. Make and Android developer build with Autconnect Profiler option enabled
3. Turn on the app and connect it to a profiler
4. In the profiler window select "Memory" section
5. Notice the "Used total" and "Total System Memory Usage" is very different and "Total System Memory Usage" is very different in different devices
Expected results: Total System Memory usage is the same with different devices with the same projects
Actual results: Total System Memory usage is very different with different devices with the same projects
Reproducible with: 2018.4.26f1, 2019.4.8f1, 2020.1.2f1, 2020.2.0a21
Note: Total System Memory usage will be a bit reworked so this case is not really a bug but a case for Total System Memory usage rework
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on WriteParticleLineVertex when the "Generate Lighting Data" property is enabled in the Particle System
- UI overlay becomes visible in ray-traced reflections when HDR Color output is enabled
- Crash on EditorOnlyPlayerSettings::GetDefaultTextureCompressionFormat when switching or opening a specific project with Android or IOS Platform
- [Mobile] Player silently crashes on a mobile device when using a lot of "Camera" GameObjects (40 and more) in the Scene
- Scene is modified after exiting Play Mode when Graphics Compositor is enabled in HD RP
Add comment