Search Issue Tracker
Fixed in 2020.2
Fixed in 2019.4, 2020.1
Votes
0
Found in
2019.2.0a8
2019.3
2019.3.10f1
2020.1
2020.2
Issue ID
1242926
Regression
Yes
Editor crashes on StageUtility::IsGameObjectRenderedByCameraAndPartOfEditableScene when calling Undo.PerformUndo() method
Reproduction steps:
1. Open the user's attached "TestUndo.zip" project
2. Click on GameObject > 3D Object > Cube in the menu bar
3. Open the Scene view
4. Select the "Cube" GameObject in the Hierarchy window
5. Change Editor tool to "Move Tool" and move the cube using Move Gizmo
6. Press Shift and W buttons on the keyboard
-- Observe the crash
Reproduces on: 2019.2.0a8, 2019.2.21f1, 2019.3.12f1, 2020.1.0b7, 2020.2.0a9
Not reproducible with: 2018.4.21f1, 2019.2.0a7
Note: an assertion before the crash "Assertion failed on expression: '!m_CurrentCamera.IsNull()'"
First lines of the stack trace:
0x00007FF6B1CD0535 (Unity) StageUtility::IsGameObjectRenderedByCameraAndPartOfEditableScene
0x00007FF6B1B7E0AB (Unity) GizmoManager::IsGizmosAllowedForObject
0x00007FF6B25A071B (Unity) EditorGUIUtility_CUSTOM_IsGizmosAllowedForObject
0x00000223D893E707 (Mono JIT Code) (wrapper managed-to-native) UnityEditor.EditorGUIUtility:IsGizmosAllowedForObject (UnityEngine.Object)
0x00000223D893E1EB (Mono JIT Code) UnityEditor.SceneView:CallOnSceneGUI ()
<...>
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
- Duplicating a Prefab instance in the Scene will cause instances of the same Prefab to be disabled and re-enabled
- GUI.Button and GUILayout.Button stay in the normal GUIStyleState even when the normal GUIStyleState is changed to another one
- Particle System mesh UV coordinates change when mesh's geometry layout is changed on import
- [Windows] The Unity import progress is not shown in the Windows taskbar
- Custom shader creation APIs are missing the AssetImportContext and thus can't handle includes correctly
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0a13
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0b12, 2019.4.0f1