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
- When a Rigidbody2D is inactive GetPoint/GetVector/GetRelativePoint/GetRelativeVector fallbacks to returning (0, 0)
- Light brightness gets intense until the 'Lightmap Encoding' quality is changed when baking Lightmap
- Crash on LinearCollectionField::LinearCollectionField after a 'm_ArrayField != SCRIPTING_NULL' assertion when opening a project
- Import Activity Window takes long time to open
- Child Canvas' Sorting Layer is changed to the same value as the parent Canvas after interacting with Dropdown UI object
Add comment