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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment