Search Issue Tracker
Not Reproducible
Votes
0
Found in
2018.1.0a6
2018.1.0b11
Issue ID
1015284
Regression
Yes
Scene with an active rigid body leaks memory
Steps to reproduce:
1. Download 1015284_repro.zip
2. Open "Test" scene
3. Check Editor memory usage (should be around 560 MB)
3. Enter play mode
4. After 1 min leave play mode
5. Check Task Manager memory usage increase by ~100 MB
Expected results: memory gets released
Actual results: memory usage increases in play mode session even when no rigid body transformation is calculated. After exiting play mode memory isn't released. After 3 playtest session Editor's memory usage can easily increase to 1 GB
Reproduced with: 2018.1.0b12, 2018.1.0a6
Not reproducible with: 2018.1.0a5, 2017.3.2f1
Regression introduced in: 2018.1.0a6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment