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
- 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