Search Issue Tracker
Fixed
Fixed in 6000.0.39f1, 6000.1.0b7, 6000.2.0a4
Votes
0
Found in
6000.0.36f1
6000.1.0b4
6000.2.0a1
Issue ID
UUM-96256
Regression
No
Crash on RaiseException when deleting animation transitions in a specific Animation Controller
How to reproduce:
1. Open the “CrashRepro“ project
2. Open the Animator Window (Window>Animation>Animator)
3. Select the “Assets/QuantumUser/Resources/Prototypes/Characters/Surgeon/Animations/SurgeonAnimator.controller“ Animator Controller
4. Delete the animation transition from “metarig_KnockbackFall“ to “metarig_Fall“
5. Delete the animation transition from “metarig_KnockbackHard“ to “metarig_Fall“
6. Delete the animation transition from “metarig_Knockback“ to “metarig_Fall“
Reproducible with: 6000.0.36f1, 6000.1.0b4, 6000.2.0a1
Couldn’t test with: 2022.3.57f1 (Errors in the Console)
Reproducible on: macOS 15.2 Sequoai (Intel), Windows 11 (reported by user)
Not reproducible on: No other environment tested
Note: The crash can occur on steps 4 or 5
First few lines of stack trace:
0x00007FFC6BB2837A (KERNELBASE) RaiseException
0x00007FFB67702D92 (Unity) LaunchBugReporter
0x00007FFB66FCAD0F (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FFB66FCB80A (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FFB67C7C3BD (Unity) DebugStringToFilePostprocessedStacktrace
0x00007FFB67C7B758 (Unity) DebugStringToFile
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
- Input from the "Backslash" key is not detected in the Web Player when using the Japanese 106/109 key keyboard
- High "Total" value of the "TerrainManager.CullAllTerrains" when generating terrain
- UI Layout rebuild triggered by a rounding error when using TextMesh Pro
- Sprite Shape Corners and Edges are invisible when a closed Sprite Shape is used
- Script icon Gizmos cause lag/performance issues in Scene view even when the Scene Camera is not pointed at Gizmos
Resolution Note (fix version 6000.2.0a4):
The crash is caused by an external package (https://github.com/BedtimeDigitalGames/Unity-Editor-History#1.4.0) that triggers a selection event on objects before assets finish importing during the editor loading process. These events are triggered within the constructor of the `EditorHistory` class which uses the `InitializeOnLoad` attribute. The class adds a selection event to the undo stack during the editor loading process, thus corrupting the undo stack once the project is loaded in. Performing any selection within the editor at that point would result in a crash when additional operations are added to the stack.
The fix introduced fully clears the undo stack once the editor has loaded in, and additional validation checks were added to the undo system to prevent crashing the editor in case the undo stack is a broken state.
Resolution Note (fix version 6000.1.0b7):
The crash is caused by an external package (https://github.com/BedtimeDigitalGames/Unity-Editor-History#1.4.0) that triggers a selection event on objects before assets finish importing during the editor loading process. These events are triggered within the constructor of the `EditorHistory` class which uses the `InitializeOnLoad` attribute. The class adds a selection event to the undo stack during the editor loading process, thus corrupting the undo stack once the project is loaded in. Performing any selection within the editor at that point would result in a crash when additional operations are added to the stack.
Resolution Note (fix version 6000.0.39f1):
The crash is caused by an external package (https://github.com/BedtimeDigitalGames/Unity-Editor-History#1.4.0) that triggers a selection event on objects before assets finish importing during the editor loading process. These events are triggered within the constructor of the `EditorHistory` class which uses the `InitializeOnLoad` attribute. The class adds a selection event to the undo stack during the editor loading process, thus corrupting the undo stack once the project is loaded in. Performing any selection within the editor at that point would result in a crash when additional operations are added to the stack.