Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.2.0a1
2019.2.0f1
2019.3.0a1
2020.1.0a1
Issue ID
1177366
Regression
No
Unity crashes when calling playable.Destroy() during the PrepareFrame()
How to reproduce:
1. Open attached project ("Playable Destroy Repro.zip")
2. Enter Play Mode
3. Check "Run Problematic Code" in the Game View
4. Press "Play Graph"
Expected result: Unity does not crash
Actual result: Unity crashes
Reproducible with - 2019.2.2f1, 2019.3.0a12, 2020.1.0a1 (Timeline 1.1.0)
Not reproducible with - 2017.4.32f1, 2018.4.7f1 (errors with packages)
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 2020.1):
Fixed in 2019.3.0b8, 2020.1.0a7