Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 5.6.X, 2017.1.X, 2017.2.X
Votes
0
Found in
5.5.3p1
Issue ID
920508
Regression
No
[Android] GPU memory of unity 5 is bigger than unity 4 with a empty scene on android platform
Steps to reproduce:
1. Open attached project with 4.7.2f1
2. Build and run to Android
3. Run "adb shell dumpsys meminfo <bundle_identifier>" command
-Total GPU memory should be around 34113KB~ (see attached image)
4. Open attached project with 5.5.3p1 or newer
5. Build and run to Android
6. Run "adb shell dumpsys meminfo <bundle_identifier>" command
-Total GPU memory should be around 102123KB~ (see attached image)
Result: GPU memory of unity 5 is bigger than unity 4
Also, there is a huge increase in Array Buffer Objects from 4.7 to 5.5 (~391 more Array Buffer Objects in 5.5)
Reproduced with: 4.7.2f1, 5.5.3p1, 2017.2.0b1
Devices under test:
Reproduced with:
Xiaomi MI 5s, OS:6.0.1, CPU:arm64-v8a, GPU:Adreno (TM) 530, Build:Xiaomi/capricorn/capricorn:6.0.1/MXB48T/V8.0.10.0.MAGCNDH:user/release-keys
Verizon SM G930V, OS:7.0, CPU:arm64-v8a, GPU:Adreno (TM) 530, Build:Verizon/heroqltevzw/heroqltevzw:7.0/NRD90M/G930VVRU4BQA2:user/release-keys
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
Add comment