Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2021.2
2022.1
2022.1.0b6
2022.2
Issue ID
1401696
Regression
Yes
Unity Editor hangs for a long time when switching to release mode after attaching C# script to Unity
How to reproduce:
1. Create a new project
2. Create a new C# script and open it
3. Click the "Attach to Unity" button
4. End Debugging
5. Go to the Unity Editor
6. In the bottom right click the bug icon
7. Click the "Switch to release mode" button
Expected result: Switching to release mode is successful
Actual result: The Editor hangs for a really long time
Reproducible with: 2021.2.0a1, 2021.2.13f1, 2022.1.0a1, 2022.1.0b9, 2022.2.0a1
Not reproducible with: 2020.3.32f1, 2021.2.14f1, 2021.2.16f1, 2022.1.0b10, 2022.1.0b13, 2022.2.0a2, 2022.2.0a8
Couldn't test with: 2019.4.36f1 (no release mode)
Reproducible with:
Visual Code Editor 2.0.14
Visual Studio Code Editor 1.2.5
Couldn't test with:
JetBrains Rider Editor 3.0.12(error attaching to Unity Editor)
Note: If you are not able to reproduce delete the Library folder and the .sln file from the project folder before opening
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
- Crash on PluginManager::RefreshPlugins when closing the Editor without making any changes with JetBrains Rider selected as the External Code Editor and Google Mobile Ads third-party plugin imported
- GetMainLight() returns incorrect distanceAttenuation value for a Custom Shader when URP Forward+ Rendering Path is used
- Standalone Profiler crash on GuidReservations::Reserve when it is opened on a specific project
- m_RenderPipelineGlobalSettingsMap or m_SRPDefaultSettings is pointing to UnityEngine.Rendering.HighDefinition.HDRenderPipeline when High Definition RP package is removed
- Rendering Debugger fields have no padding at the bottom of the fields list
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.14f1, 2022.1.0b10, 2022.2.0a2