Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X, 2019.2.X
Votes
0
Found in
2018.3.0f2
2018.3.12f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1166522
Regression
No
Unity runs out of RAM after calling GameObjectRecorder.SaveToClip(clip)
How to reproduce:
1. Open the attached project
2. Open the "sadas.unity" scene
3. Press Play
Actual result: Unity crashes with out of RAM dialog.
Reproducible with: 2018.3.0f2, 2018.3.14f1, 2018.4.3f1, 2019.1.8f1, 2019.2.0b8, 2019.3.0a8.
Notes:
The GameObjectRecorder isn't implemented in 2017.4 and 2018.3 alpha.
----------------------
Fixed in 2018.4.7f1, 2019.2.1.f1, 2019.3.0a10.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
Add comment