Search Issue Tracker
By Design
Votes
0
Found in
2018.1.0b3
Issue ID
990837
Regression
No
GPU Usage Profiler disappears each time Unity is re-opened
How to reproduce:
1. Create or open Unity project
2. Go to Window --> Profiler
3. Click on Add Profiler and add GPU profiler
4. Save the project and close it
5. Re-open it and go to Window --> Profiler
Expected result: GPU Usage profiler is still among other profilers
Actual result: GPU Usage profiler is not among other profilers, you have to manually add it again
Reproducible with - 2018.1.0b4, 2017.3.0p3, 2017.2.1p2, 2017.1.3f1
Note: this is by design because having the GPU chart opened means profiling GPU, which in turn means a huge profiling overhead right after opening the profiler window.
However, we'll redesign how profiler areas are set to actively profile or just be "muted" in the future. This means, GPU chart would stick around and just reset to muted.
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
- OnPostprocessAllAssets() is not called for a modified Prefab when another Asset is set Dirty in the same callback
- [Android] UIToolkit ClickEvent is fired when the device is rotated
- Compilation errors occur when "uintBitsToFloat(int)" gets used in OpenGLES
- User Reporting does not send reports when Managed Stripping Level is set to Low or higher
- Editor crashes and a window with "GetManagerFromContext: pointer to object of manager 'MonoManager' is NULL (table index 5)" error is thrown when launching a project with a corrupted library
Resolution Note (2020.1.X):
This is by design because having the GPU chart opened means profiling GPU, which in turn means a huge profiling overhead right after opening the profiler window.
However, we'll redesign how profiler areas are set to actively profile or just be "muted" in the future. This means, GPU chart would stick around and just reset to muted.