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
- "Debug Assertion Failed!" error when launching Windows Dedicated Server Player with Script Debugging enabled
- [Cinematic Studio][3D HDRP] Shader warnings thrown in the Console window when creating a new project with Cinematic Studio template
- Autoplay is triggered on Audio Assets when changing Asset Bundle tags
- Inspector Asset Bundle section has no indication for Variants, AssetBundle is written without a space, and Variant dropdown menu is available without setting the Asset Bundle first
- Graphics.DrawProceduralIndirect and Graphics.DrawProceduralNow silently dropped on DX12
Add comment