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
- 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