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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Add comment