Search Issue Tracker
By Design
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2019.1.0a1
2019.1.0b3
2019.2.0a1
Issue ID
1126835
Regression
No
Depending on the placement of the GCU profiler, the global GPU usage pattern drawn is different
Steps to reproduce:
1. Open attached project "case_1126835"
2. In the Profiler window on the top click "Add Profiler" and press GPU
3. Press Play
4. Click on the Profiler window and drag it anywhere
5. Notice GPU usage in the Profiler window while dragging the Profiler window
Expected results: GPU usage does not change when dragging Profiler window
Actual results: GPU usage goes up while dragging the Profiler window
Reproducible with: 2017.4.20f2, 2018.3.6f1, 2019.1.0b3, 2019.2.0a5
Additional information: the "pattern" of usage as showed by the profiler actually depends on the size of the window that we draw.
So basically it is the profiler itself that affects the results - redrawing the profiler is slow and it consumes additional resources.
These issues should be solved by the current reworking done on the profiler, so I will close the issue.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (2019.2.X):
Windows in Unity are being redrawn when dragged. Profiler window contains more UI elements than normal window - charts and timeline are more expensive to draw.
It is expected when additional redraws on mouse move cause higher GPU load. Normally ProfilerWindow is updated every 200ms.