Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.10f1
Issue ID
1098937
Regression
No
Cloned StateMachineBehaviour don't get destroyed after each script recompile
How to reproduce:
1. Open the user-submitted project and open to the "samplescene" scene
2. Open the Console Window and observe the count on the StateMachineBehaviour debug messages
3. Clear the Console Window
4. Open the "MyStateMachineBehaviour" script and comment out the 10th line to force a recompile
5. Get back to Unity and observe the Console Window again
Expected result: the StateMachineBehaviour debug.log message count stays the same (5)
Actual result: the StateMachineBehaviour debug.log message count increases with each script recompile
Reproduced in: 2019.1.0a8, 2018.3.0b10, 2018.2.16f1, 2018.1.9f2, 2017.4.15f1
Comments (2)
-
imarkroger
Nov 09, 2018 07:57
~Removed~
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Leak on an edge-case workflow. Only happens in editor. Will not fix.