Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.2.0f3
Issue ID
969183
Regression
Yes
[WWW][iOS] WWW.texture takes up more memory in Unity 2017 compared to 5.6
Steps to reproduce:
1. Download the projects for 5.6 and 2017 versions
2. Build each of them and deploy to an iOS device (developer mode with "Autoconnect Profiler" should be enabled)
3. In Unity under "Profiler" window, select device the build is running on under "Active Profiler"
4. Check the detailed memory usage
Results:
5.6 - 23.1MB of ram used, Scene Memory takes up 8.8MB, out of which Texture2D - 8.8MB
2017.3 - 35.7MB of ram used, Scene Memory takes up 11.6MB, out of which Texture2D - 11.1MB
Reproduced with: Unity 2017.1.2p1, 2017.2.0p1, 2017.3.0b9
Reproduced on: iPad 3 Mini, iOS 10.3.2
Note: UnityWebRequest uses the same amount of memory in 5.6 and 2017 versions.
___
Issue will not be fixed: Since this issue does not reproduce using UnityWebRequest, it won't be fixed, please use UnityWebRequest.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
- Audio Mixer “+” buttons overlap with UI when the Audio Mixer window layout is set to Horizontal
- "Clear" button in the "Set project display name" closes all the pop-up instead of clearing just a name from the field
- Video Player renders no video on specific devices when using Vulkan
- The Editor slows itself down by showing tons of warnings when the majority of TransformAccessArrays content are NullRefs
Add comment