Search Issue Tracker
Active
Votes
1
Found in
2019.4
2019.4.38f1
2020.3
2021.3
2022.1
2022.2
Issue ID
1422924
Regression
No
Crash when exiting the Play Mode and there's a script attached to a GameObject with "gameObject.hideFlags = HideFlags.DontSave;"
Reproduction steps:
1. Open the attached project
2. Enter the Play Mode
3. Exit the Play Mode
4. Observe the crash
Expected result: the Play Mode should stop
Actual result: Editor crashes
Reproducible with: 2019.4.39f1, 2020.3.35f1, 2021.3.3f1, 2022.1.2f1, 2022.2.0a15
Reproducible on: Windows 10 (21H2)
First few lines of the stack trace:
0x00007FF6CEF2EC84 (Unity) SceneDataContainer::GetSceneData
0x00007FF6CEF2F141 (Unity) SceneDataContainer::HasData
0x00007FF6CEF2D284 (Unity) SceneVisibilityState::AreAllChildrenVisible
0x00007FF6CFAB1326 (Unity) SceneVisibilityState_CUSTOM_AreAllChildrenVisible
0x000001FAE70312EE (Mono JIT Code) (wrapper managed-to-native) UnityEditor.SceneVisibilityState:AreAllChildrenVisible (UnityEngine.GameObject)
0x000001FAE703114B (Mono JIT Code) UnityEditor.SceneVisibilityManager:AreAllDescendantsVisible (UnityEngine.GameObject)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment