Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3
2021.3
2022.1
2022.2
2022.2.0a10
Issue ID
1419472
Regression
No
Standalone Profiler starts to profile frames in Play Mode when reopening after closing in Edit Mode
How to reproduce:
1. Create a new empty project
2. Open the Profiler Window Standalone (Window -> Analysis -> Profiler (Standalone Process) )
3. Change the Profiler to show Edit Mode
4. Close the Profiler Window and reopen it again as a Standalone Window
Expected result: Nothing is being profiled due to the window being opened in Play Mode
Actual result: The Profiler is still profiling even though the frames shown are in Play Mode
Reproducible with: 2020.3.34f1, 2021.3.1f1, 2022.1.0f1, 2022.2.0a11
Couldn't test with: 2019.4.38f1 (Not possible to open Profiler as a Standalone Process)
Note:
- Not reproducible with normal Profiler Window
- Reported on Windows 10, reproduced on macOS
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:
Standalone Profiler is in support mode for critical bugs only. Given the low user pain index we decided to not fix the issue