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)
-
solitairegamesfree
Apr 09, 2019 07:51
Hi, guys, I have the best trick for you. you can use your pc screen for multiple works using windows 10 slip screen https://windowsclassroom.com/how-to-split-screen-on-windows-10 if you don't know how I do then visit our website thank you
-
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
- Incorrect Shader keyword activation for Shadows when no Light is present in URP
- Editor freezes when loading a specific AssetBundle
- WebGPU builds with Multithreading enabled crash on Safari
- Set as Value in UI Builder doesn't work across all properties.
- Calculating time durations in RenderDoc with DX12 causes 'Device Lost error' popup
Resolution Note:
Leak on an edge-case workflow. Only happens in editor. Will not fix.