Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2021.2.0b6
2022.1
2022.1.0a3
Issue ID
1352271
Regression
Yes
Editor throws a crash message when closing Standalone Profiler Window
How to reproduce:
1. Create a new project
2. Click Window -> Analysis -> Profiler (Standalone Process)
3. Wait for the process to finish opening the Profiler and then close the Profiler Window
Expected results: The Profiler's process is closed without any issues
Actual results: The Profiler's process crashes when trying to close the window
Reproducible with: 2021.2.0b6, 2022.1.0a1, 2022.1.0a3
Not reproducible with: 2020.3.14f1, 2021.1.16f1, 2021.2.0b5, 2022.1.0a4, 2022.1.0a6
Could not test with: 2019.4.29f1 (Standalone Profiler process was not available)
Reproducible on - macOS 11.4 and Windows10 (Tested with 2021.2.0b2 - didn't reproduce the issue; 2022.1.0a3 - reproduced the issue)
Notes:
1. The crash seems to occur only for the Profiler's separate process. So while a crash window is thrown, the Editor can still be used afterward
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
- Any small change in UI Builder Inspector refreshes Editor Inspector
- Inaccurate Box Collider boundaries on a rotated child Cube when the parent GameObject Scale is non-uniform
- [Android] "SHADOWS_SCREEN" set as shader Keyword when no "_ShadowMapTexture" is bound leads to freeze on a build on some Mali GPU devices
- The global scene list is overridden in a project built with command line when the Override Global Scene List setting is disabled in the build profile
- Global Scenes are not included in the Build when building multiple Build Profiles at the same time
Resolution Note (fix version 2022.1):
Fixed in Unity 2022.1.0a4