Search Issue Tracker
By Design
Votes
0
Found in
2018.1.0b12
Issue ID
1017582
Regression
No
Profiler.GetAllocatedMemoryForGraphicsDriver() always returns 0 in non-dev builds
Steps to reproduce:
1. Open "GetAllocatedMemoryForGraphicsDriver" project
2. Build for Windows standalone and run (development mode off)
-Profiler.GetAllocatedMemoryForGraphicsDriver() will return 0 (first line of output in the game view)
Expected result: for consistency, GetAllocatedMemoryForGraphicsDriver method should return valid value just like other Profiler methods do
Actual result: GetAllocatedMemoryForGraphicsDriver method always returns 0 in non-dev builds
Reproduced on: 2018.1.8f1, 2018.2.0f2, 2018.3.0a4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Fixing Message Loss in UMPE During Domain Reload
- The Editor freezes when ScheduleReadOnly of IJobParallelForTransform with dependency is used
- Text is truncated in the Inspector when the display scale is set to 150%
- CancellationTokenSource(<timeout>) has incorrect cancellation status when used in WebGL Player
- VFX property value names are cut off when properties with 'Arc' are viewed in the VFX Blackboard
Add comment