Search Issue Tracker
Not Reproducible
Votes
0
Found in
2019.3
2020.1.0b3
2020.2
Issue ID
1234717
Regression
No
Profiler performance drops significantly when opening and closing the Standalone Profiler
How to reproduce:
1. Open the attached (Standalone Profiler Issue.zip) project
2. Open the Profiler Window (Window -> Analysis -> Profiler)
3. Enter the PlayMode -> Pause it after few seconds
4. Open the Standalone Profiler (Window -> Analysis -> Profiler(Standalone Process))
5. Once the Standalone Profiler has opened - close it
6. Enter the PlayMode -> observe the Profiler
Expected results: Profiler performance stays the same as it was before opening and closing the Standalone Profiler
Actual results: Profiler performance drops significantly when opening and closing the Standalone Profiler (see Performance.png)
Reproducible with: 2019.3.14f1, 2020.1.0b9, 2020.2.0a11
Notes:
- Could not test on 2018.4 and lower, because Standalone Profiler does not exist in these versions
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment