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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Add comment