Search Issue Tracker
Not Reproducible
Votes
5
Found in
5.5.0p4
Issue ID
871653
Regression
Yes
Abstract StateMachineBehaviour causes crash when there is a single sub-state machine
Reproduction steps:
1. Open project attached (StateMachineBehaviour_Bug.zip)
2. Open scene "Scene_Crash"
3. Press Play.
Expected result: Scene plays.
Actual result: Unity crashes. (Not always).
Note: If it does not reproduce from first try, stop scene and play again. It might crash from the first try but can also take about 10-50 attempts.
Crash does not appear when using simple class or there are more than one sub-state machine.
Reproduced on: 5.5.0p3, 5.5.0p4, 5.6.0a6, 5.6.0b1 5.6.0b4; 5.5.1p3; 5.5.1f1
Not reproducible on: 5.5.0f3, 5.5.0p1. (Not sure, it might be even harder to reproduce on these versions)
Note: Bug is still reproduced in Case: 879847
Comments (1)
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
- Editor crashes and a window with "GetManagerFromContext: pointer to object of manager 'MonoManager' is NULL (table index 5)" error is shown when launching a freshly created project
- Editor Windows dragging behavior is erratic/glitchy when a specific multi-display setup is used and the Editor window is not on the main display
- Meta Quest missing an icon in Build Profiles window in U6.0
- Foldout arrow indent is misaligned in the Inspector when used for Arrays or Lists
- Material import pipeline strips properties when it is added with a script
YannAppeal
Feb 03, 2017 00:52
We have the same problem here since 5.5.0p3. I will try to do a repro and submit the issue. It sound like it is related to the multithreaded evaluation of the StateMachine...