Search Issue Tracker
By Design
Votes
0
Found in
2017.3.0f3
Issue ID
1045111
Regression
No
Heavy memory leak on creating 2D Array
How to reproduce:
1. Open the user-submitted project
2. Create a new empty game object and attach the MapGenerator script
3. In the Inspector Window change the values of "Width" and "Height"
4. Observe the Task Manager
Expected result: The values are inputted correctly
Actual: Unity leaks memory and freezes
Reproduced in: 2018.3.0a1, 2018.2.0b7, 2018.1.4f1, 2017.4.5f1, 2017.2.3f1, 2017.1.4p1
Note: Changing the Scripting runtime did not have any effect
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