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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
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