Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.8f1
2019.1.0a1
2019.2.0a1
Issue ID
1139438
Regression
No
Memory Profiler reporting 4x lower Texture2D memory usage when Texture Streaming is enabled
Steps to reproduce:
1. Open Project "MemoryProfilerBug"
2. Profile Memory on Build with Texture Steaming enabled
3. Take a Snapshot of Detailed Profile, see Assets -> Texture2D
4. Profile Memory on Build with Texture Steaming disabled
5. Take a Snapshot of Detailed Profile, see Assets -> Texture2D
6. The values don't differ by a factor of 4
Expected result: Texture2D memory allocation is independent of Texture Streaming Option
Actual result: Texture2D memory allocation as reported by the Profiler is dependent on Texture Streaming Option
Reproducible with: 2017.4.24f1, 2018.3.11f1, 2019.1.0b9, 2019.2.0a10
Note: Reproducible with the new Memory Profiler as well
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment