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
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Duplicated groups and incorrect grouping in UI Builder when using UxmlElementAttribute: libraryPath
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
- Crash on UNITY_FT_Render_Glyph_Internal when Generating Font Atlas in the Font Asset Creator Window
Add comment