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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Add comment