Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.2.X, 2017.3.X
Won't Fix in 2017.1.X
Votes
1
Found in
2017.1.0f3
Issue ID
931748
Regression
No
Project leaks memory between plays
Steps to reproduce:
1. Open attached project "931748.zip"
2. Open Task Manager and look at Unity's memory usage
3. Open "Main" scene (make sure Game View aspect ratio is 16:9)
4. Enter play mode
5. Wait for cubes to spawn and use LMB to destroy them
6. Exit play mode
7. Open Task Manager and look at Unity's memory usage
8. Repeat steps 4-8
Actual result: Editors memory usage increases after each play
Reproducible with: 5.6.2p4, 2017.1.0f3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment